mail.google.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

53risk

Elevated

Several issues worth triaging this week.

0Critical

2High

1Medium

2Low

1Info

Collected 20 hours ago20.3sfrom cache

Certificate Transparency
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs10
Registration
DNS posture0
Email authentication0
Certificate
Security headers5
Archived URLs
Analysis6

noteCertificate Transparency did not complete (HTTP 404). Results below are partial.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://accounts.google.com/v3/signin/identifier?continue=https://mail.google.com/mail/u/0/&emr=1&followup=https://mail.google.com/mail/u/0/&osid=1&passive=1209600&service=mail&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S2066537071:1788711664214705
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.mail.google.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@mail.google.com"`, review the reports, then move to p=quarantine and p=reject.
asset: mail.google.com
Nothing tells receiving mail servers which hosts may send as @mail.google.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: mail.google.com
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://accounts.google.com/v3/signin/identifier?continue=https://mail.google.com/mail/u/0/&emr=1&followup=https://mail.google.com/mail/u/0/&osid=1&passive=1209600&service=mail&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S2066537071:1788711664214705
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: mail.google.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: mail.google.com

final https://accounts.google.com/v3/signin/identifier?continue=https://mail.google.com/mail/u/0/&emr=1&followup=https://mail.google.com/mail/u/0/&osid=1&passive=1209600&service=mail&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S2066537071:1788711664214705status 200time 1704msstack cloudflare

✗http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains
✓Content-Security-Policy
script-src 'report-sample' 'nonce-lFEMHk8Hkx8nnUB8h2pQBA' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /v3/signin/_/AccountsSignInUi/cspreport;w…
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
✓Permissions-Policy
ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-form
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __Host-GAPS
Secure · HttpOnly · no SameSite

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓0 nameservers

✓Registered with MarkMonitor Inc.29.0 years old
google.com
✓Registration expiry738 days
2028-09-14
✓Transfer lock
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
✓4 nameservers at registry
ns1.google.com ns2.google.com ns3.google.com ns4.google.com

Address	Ports	Edge	Network
74.125.68.83 mail.google.com +1	80443843	direct	—
74.125.68.18 mail.google.com +1	80443843	direct	—
74.125.68.19 mail.google.com +1	80843	direct	—
74.125.68.17 mail.google.com +1	80443	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

mail.google.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames