Skip to content
https://tomtom.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.tomtom.com/
200https://tomtom.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://tomtom.com/ https://www.tomtom.com/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
A+
DNS Records
1 A records, 15 ms lookup
PASS
1 A records, 15 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 98.64.11.144
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: dns3.p09.nsone.net, dns2.p09.nsone.net, dns4.p09.nsone.net, a1-248.akam.net, dns1.p09.nsone.net
Info::
1 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: 15 ms
Got: 15 ms
A98.64.11.144
AAAA
CNAME
NSdns3.p09.nsone.net, dns2.p09.nsone.net, dns4.p09.nsone.net, a1-248.akam.net, dns1.p09.nsone.net
MX
10 tomtom-com.mail.protection.outlook.com
TXT
anthropic-domain-verification-8y51pm=LXGAoEDAJgHW2aqo7vJ8muOR3
unity-sso-verification=cb42482b-80c0-4c31-8f46-9eec1f11be9c
miro-verification=c366a88d6ef9552f4a93d9016e5eb3b8ec5d47bb
airtable-verification=f87a384c2ed70508a7caf734c8fc56e9
google-site-verification=GzfIXCzElSCZaGP3KID04CgZ-JIxTa2KDF5kOPiuxbE
90e4ae7308c543e59bc45ad2c7c0c6ba
atlassian-domain-verification=LNTzFCPe79DXpAt4NY1pKp5ZNIuZFPoQQ00EHwKjcQX1W0QLQD...
google-site-verification=AIX2eLQtiGKMjrdTkaNIjlibc69ZhosNZEQU4XvvDPY
google-site-verification=UzHGW9mOc94-x3sIA1aH0UDc2t8EGPIWewIT72bMVBM
b3hqxdn8mym6085y5qjjmglycyytzvgf
docusign=4e2ef447-c398-49eb-885f-93a3c38cb230
teamviewer-sso-verification=d61bf8d9f45847469ee7545563807b70
onetrust-domain-verification=ed9b028f470a4f418effe0bb8faf3af8
RV = QuoVadis=b7857c09-11e4-4c65-8a10-df1305b6642a
SPF v=spf1 include:spf.protection.outlook.com include:sharepointonline.com include:_...
docusign=3ce7bb6d-7e84-47a7-8d4f-dcd7de13f634
perplexity-ai-domain-verification-m8v330=6esKkg6MCeHEUKGqgGLE81uQD
adobe-idp-site-verification=a0c9aec7-2cac-4280-b67d-87c4a648f73b
hcp-domain-verification=865afc456cf26f92967c598d0c27a913040e4e23b8167e02f022db1a...
facebook-domain-verification=cpwht607889mbpsxlzqbrtvmmgwm93
h1-domain-verification=9cZmw66YqZ1Nb3DAMtPQYPRurXKQ3kgX7KTT8ypD1NU1WxC2
MS=ms14080619
apple-domain-verification=NAGVDc5TxR8AvHUb
pardot510681=40442bb65425b211ae9d2d6de714659b41600748d54e1e6ac7faeed415190f48
sBHbq68WlBeeFpBU7TsF/rILV+UblLl61eL3JN2uZ3vhCQKmqm9PuYvxrVOC4Nird0r0Z/AmPTfRDCx0...
onetrust-domain-verification=829e27e3ec234967a16cbe0f3bae485c
mixpanel-domain-verify=110ce23e-aadd-4988-aa46-039138657559
jamf-site-verification=G3E8_z6Hul8V4LRRzqb36g
google-site-verification=WO42AZ7OcwAQhtl5RmaR0dlngJYc0bqbypY3bhH6XbM
ms-domain-verification=5808bf5a-1792-495f-b5f1-e33e1cf1390c
google-site-verification=fY7o80hMancXdF59CPD2XUPr5ck9JySV-jwgufbHbVE
docker-verification=2158b838-492e-404d-90c3-21764f1c446e
identrust_validate=kd87DM2Y38a5BnE5BuxrsDk6IprSXLXpeozwkf9JGU1O
_1zn25sqh83sr0ztkqv4a4pndmifje6u
CAALookup not available with standard resolver
Resolved in 15 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), 35 ms total
PASS
1 redirect(s), 35 ms total
Info::
Single redirect
Got: https://tomtom.com → https://www.tomtom.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://tomtom.com

https://tomtom.com

17 ms · HTTP/1.1

302

https://www.tomtom.com/

18 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tomtom.com30217 msHTTP/1.1Microsoft-Azure-Application-Gateway/v2
2https://www.tomtom.com/20018 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 336 URLs
PASS
robots.txt present, sitemap with 336 URLs
Info::
robots.txt is present
Got: 448 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 336 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 448 B Sitemaps referenced 2 User-agents Claude-SearchBot, *, OAI-SearchBot, ChatGPT-User, PerplexityBot, AndiBot, ClaudeBot, Claude-User Blocking No — crawling allowed
# Algolia-Crawler-Verif: 9AA02D11F8C5425D885

User-agent: *
Disallow: */search/
Disallow: */account/
Disallow: /newsroom/tag/

# Allow AI search and agent use

User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: PerplexityBot
User-agent: AndiBot
User-agent: ClaudeBot
User-agent: Claude-User
User-agent: Claude-SearchBot
Allow: /


Sitemap: https://www.tomtom.com/sitemap.xml
Sitemap: https://www.tomtom.com/en_gb/navigation/sitemap.xml

A+
Domain Intelligence
tomtom.com — via MarkMonitor Inc., 30 years, 7 months old, hosted on Microsoft Azure
PASS
tomtom.com — via MarkMonitor Inc., 30 years, 7 months old, hosted on Microsoft Azure
Info::
Domain registered until Feb 24, 2027 (10 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.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

253 days

February 24, 2027

SSL certificate

195 days

Issued by IdenTrust

Domain age

30 years, 7 months

Registered February 23, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

98.64.11.144

Registrar

MarkMonitor Inc.

Unlocked 5 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 February 23, 1996 (30 years, 7 months ago)
Expires February 24, 2027 (10 months)
Last Updated January 23, 2026
Name Servers a1-248.akam.net, dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net
DNSSEC Not enabled
Hosting
IP Address 98.64.11.144
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.2s)

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 18 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
2 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
9 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
18 ms
Total Time Total request time from DNS lookup through full response.
19 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 9 ms TLS Handshake 5 ms Server Processing 2 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