Digital exposure report
waze.com
Low exposure. The domain is well protected in most areas checked.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS waze.com
- 2.
Turn off browser features your site does not use
This limits access to things like camera or location if a page is misused.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://waze.com/ | grep -i "Permissions-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- waze.com
- Website request
- GET https://waze.com/ → https://www.waze.com/
- Scan time
- 2026-11-19 02:59:48 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 29/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 28/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 1 of 10 DNS lookups.
v=spf1 include:_spf.google.com ~all
$ dig +short TXT waze.com
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
$ dig +short TXT _dmarc.waze.com
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCQdUTtXUOIXQ+FrspRD1S4uLnWT2EjlztT… s1._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1thuDmcp4f1U6WFxp8J0MI0nGvujorb6aJHv0… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAHLMnB6iVlvTWKsuSTM/lZqe1tWdRxaV68c7q…
$ dig +short TXT google._domainkey.waze.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com 30 alt2.aspmx.l.google.com 20 alt1.aspmx.l.google.com
$ dig +short MX waze.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://waze.com/ returned HTTP 200 (final URL: https://www.waze.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.waze.com/
$ curl -sIL https://waze.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://waze.com/
HTTP 301 Location: https://waze.com/
$ curl -sI http://waze.com/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.
Live TLS handshake: certificate accepted The CT log service was unavailable at the time of the check Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect waze.com:443 -servername waze.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=63072000 (730 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
$ curl -sIL https://waze.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Passed · Severity: OK · 8/8The site restricts which scripts are allowed to run.
CSP is set without permissive sources in script-src.
Content-Security-Policy: default-src * blob: data:; script-src 'report-sample' https://accounts.google.com/gsi/client https://googleads.g.doubleclick.net/pagead/viewthroughconversion/ https://www.google-analytics.com/analytics.js https://www.google.com/recaptcha/api.js https://www.googletagmanager.com https://www.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.js https://www.gstatic.com/marketing-cms/reviewed-scripts/ https://www.gstatic.com/recaptcha/releases/; object-src 'none'; style-src 'unsafe-inline' *; report-uri https://csp.withgoogle.com/csp/corp-marketing-cms-team; base-uri 'self', script-src 'nonce-8erlpQAAtVqedCXcded9yA' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/waze-marketing-team; base-uri 'none', require-trusted-types-for 'script'; report-uri https://csp.withgoogle.com/csp/waze-marketing-team
$ curl -sIL https://waze.com/ | grep -i "Content-Security-Policy"
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://waze.com/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://waze.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://waze.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://waze.com/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://waze.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS waze.com: NODATA
$ dig +short DS waze.com
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec waze.com SOA delv waze.com
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "pki.goog" | 0 issuewild "pki.goog"
0 issue "pki.goog" 0 issuewild "pki.goog"
$ dig +short CAA waze.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns-cloud-b4.googledomains.com ns-cloud-b2.googledomains.com ns-cloud-b1.googledomains.com ns-cloud-b3.googledomains.com
$ dig +short NS waze.com
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.0No gaps observed
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baselineNo gaps observed
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | waze.com | 130.211.9.172 |
| AAAA | waze.com | 2600:1901:0:b230:: |
| MX | waze.com | 10 aspmx.l.google.com | 40 aspmx2.googlemail.com | 50 aspmx3.googlemail.com | 30 alt2.aspmx.l.google.com | 20 alt1.aspmx.l.google.com |
| NS | waze.com | ns-cloud-b4.googledomains.com | ns-cloud-b2.googledomains.com | ns-cloud-b1.googledomains.com | ns-cloud-b3.googledomains.com |
| TXT | waze.com | 16ra/0Xa4iKpOWPnK72tHaroVGQsuMznJmDEDmBusu1C6e/4+b4E3SeTLrx5fR986eGa7tZpf7eLhzEZcUwy/E5+xOYAmRhIXkWN1AukAurkqYFfWb0GpJBDnRvh8GPeG/S+P5wLQEe/LZMD1EN0gwjPELlE/j6JzrITIHejrJjdPDdJblqYibXrV8QqKc5LyK9I6dFjwWlRtuCC91hX21YxkRz+4QIDAQAB | google-site-verification=nSaHA9lIP9L3gFJQEYxtSwHY88MBSrwRXlZ-vLztW04 | google-site-verification=N2mW-L25o-v4q4LkryQS55pL_C8CnsIL8-FpZUZtKEg | google-site-verification=A2cp78UVYzrRvmujIIRO1QGJ2qIduJDJEPaJSxy0RsI | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAssPYphcnIMFiOS7ol1k6dJs14MLaA1cEiw8WOe8cNnLbvtcOtGBqhQmgvGGCapKX+B18HKCUTbnduTuOmKxzAThqoqMu2F22kSSWBf5q5mL5aM7XEc7w9wKG | v=spf1 include:_spf.google.com ~all | google-site-verification=k0_7da8Nm3RA9ZFG-8Nj2895hmeUdDr3RuP1vQVNyOs | v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCQdUTtXUOIXQ+FrspRD1S4uLnWT2EjlztTB9/3upH3HsuOArbtSJoWXFuFj7ehPG47hmvBSr0lRHIB3rpb79WfgbntQ1p4wVO9U4RYA+Cbq7M++7n2BSjvFFOkQ9IC8TWJYeOM6ECO1Namizw1EsiTzOSqHQ5D0zWZbyHKom1aWQIDAQAB | v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCYDCQ5ZlVEeUdMEopVa0bdjsTo+5JTdS+25aP+kPGoFNtzNG7No+64qoX9HuZvCe7sjmUncSCV2oEbdxgJvB/ODQ5cS3Px/qaqagn/ZXUBzgbtvHSEXV+ugH52us0i/i041qd0KHa6v/82Dg5XofyuDi+QgUoBa+hcw5JsqfKssQIDAQAB |
| TXT | _dmarc.waze.com | v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com |
| CAA | waze.com | 0 issue "pki.goog" | 0 issuewild "pki.goog" |
| DS | waze.com | — |