Skip to content
https://waze.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.waze.com/
200https://waze.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://waze.com/ https://waze.com/

Consistent

B
TLS Certificate Expiry & Recommendations
57 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

57
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 121 ms lookup
PASS
1 A records, 121 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 130.211.9.172
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2600:1901:0:b230::
Info::
4 nameserver(s) configured
Got: ns-cloud-b1.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 121 ms
Got: 121 ms
A130.211.9.172
AAAA2600:1901:0:b230::
CNAME
NSns-cloud-b1.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
TXT
google-site-verification=nSaHA9lIP9L3gFJQEYxtSwHY88MBSrwRXlZ-vLztW04
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCQdUTtXUOIXQ+FrspRD1S4uL...
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCYDCQ5ZlVEeUdMEopVa0bdjs...
16ra/0Xa4iKpOWPnK72tHaroVGQsuMznJmDEDmBusu1C6e/4+b4E3SeTLrx5fR986eGa7tZpf7eLhzEZ...
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAssPYphcnIMFiOS7ol1...
google-site-verification=k0_7da8Nm3RA9ZFG-8Nj2895hmeUdDr3RuP1vQVNyOs
SPF v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:_spf.centerco...
google-site-verification=A2cp78UVYzrRvmujIIRO1QGJ2qIduJDJEPaJSxy0RsI
google-site-verification=N2mW-L25o-v4q4LkryQS55pL_C8CnsIL8-FpZUZtKEg
CAALookup not available with standard resolver
Resolved in 121 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 531 ms total
PASS
1 redirect(s), 531 ms total
Info::
Single redirect
Got: https://waze.com → https://www.waze.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 531 ms total
Got: 531 ms

https://waze.com

190 ms · HTTP/1.1

301

https://www.waze.com/

340 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://waze.com301190 msHTTP/1.1Google Frontend
2https://www.waze.com/200340 msHTTP/1.1Google Frontend

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (3 ms)
PASS
IPv6 reachable (3 ms)
Info::
IPv6 is configured and reachable at 2600:1901:0:b230::
Got: 3 ms connect
IPv6 Ready
AAAA Records 2600:1901:0:b230:: Connection Reachable (3 ms)
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 1223 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
Sitemap index with 5 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1223 B Sitemaps referenced 1 User-agents semrushbot, ahrefsbot, blexbot, seo spider, Googlebot, *, mauibot Blocking No — crawling allowed
User-agent: mauibot
Disallow: /discuss/

User-agent: semrushbot
Disallow: /discuss/

User-agent: ahrefsbot
Disallow: /discuss/

User-agent: blexbot
Disallow: /discuss/

User-agent: seo spider
Disallow: /discuss/

User-agent: Googlebot
Disallow: /discuss/admin/
Disallow: /discuss/auth/
Disallow: /discuss/assets/browser-update*.js
Disallow: /discuss/email/
Disallow: /discuss/session
Disallow: /discuss/user-api-key
Disallow: /discuss/*?api_key*
Disallow: /discuss/*?*api_key*

User-agent: *
Disallow: /discuss/admin/
Disallow: /discuss/auth/
Disallow: /discuss/assets/browser-update*.js
Disallow: /discuss/email/
Disallow: /discuss/session
Disallow: /discuss/user-api-key
Disallow: /discuss/*?api_key*
Disallow: /discuss/*?*api_key*
Disallow: /discuss/badges
Disallow: /discuss/my
Disallow: /discuss/search
Disallow: /discuss/tag/*/l
Disallow: /discuss/g
Disallow: /discuss/t/*/*.rss
Disallow: /discuss/c/*.rss

Disallow: /reporting
Disallow: /Descartes
Disallow: /RoutingManager
Disallow: /row-RoutingManager
Disallow: /il-RoutingManager
Disallow: /signin
Disallow: /ul
Disallow: /_user/api
Disallow: /live-map/api
Allow: /live-map/api/venues
Allow: /.well-known/assetlinks.json

Sitemap: https://www.waze.com/sitemap.xml
A+
Domain Intelligence
waze.com — via MarkMonitor Inc., 26 years, 5 months old
PASS
waze.com — via MarkMonitor Inc., 26 years, 5 months old
Info::
Domain registered until Apr 1, 2027 (11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

260 days

April 1, 2027

SSL certificate

57 days

Issued by Google Trust Services

Domain age

26 years, 5 months

Registered April 1, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1901:0:b230::

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created April 1, 2000 (26 years, 5 months ago)
Expires April 1, 2027 (11 months)
Last Updated February 28, 2026
Name Servers ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 2600:1901:0:b230::
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 251 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
57 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
64 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
251 ms
Total Time Total request time from DNS lookup through full response.
251 ms

Connection waterfall

DNS Lookup 57 ms TCP Connect 3 ms TLS Handshake 64 ms Server Processing 128 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback