Skip to content
https://www.garmin.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
4 PASS 5 REVIEW
B
DNS Records
2 A records, 16 ms lookup
REVIEW
2 A records, 16 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.148.16, 104.17.147.16
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.garmin.com.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 16 ms
Got: 16 ms
A104.17.148.16, 104.17.147.16
AAAA—
CNAMEwww.garmin.com.cdn.cloudflare.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 16 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
Redirect Chain
2 redirect(s), 532 ms total
REVIEW
2 redirect(s), 532 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.garmin.com
Info::
Redirect overhead: 532 ms total
Got: 532 ms
Info::
Cross-domain redirect detected

https://www.garmin.com

40 ms · HTTP/1.1

302

https://www.garmin.com/pt-BR/

63 ms · HTTP/1.1

301

https://www.garminstore.com.br/

430 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.garmin.com30240 msHTTP/1.1cloudflare
2https://www.garmin.com/pt-BR/30163 msHTTP/1.1cloudflare
3https://www.garminstore.com.br/200430 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

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

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

Certificate validity

75
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9e8bbc111e56f2e4-GRU
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bbc111e56f2e4-GRU
A+
Crawlability
robots.txt present, sitemap with 65 URLs
PASS
robots.txt present, sitemap with 65 URLs
Info::
robots.txt is present
Got: 1083 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 65 entries
Info::
Sitemap index with 65 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1083 B Sitemaps referenced 4 User-agents UptimeRobot, ClaudeBot, Claude-Web, cohere-ai, Meta-ExternalAgent, Quora-Bot, Better Uptime Bot, omgili, TurnitinBot, *, gsa-garmin, anthropic-ai, GPTBot, ecoresearchCrawler, EyeMonIT Uptime Bot, CCBot, ChatGPT-User, DataForSeoBot, DuckAssistBot, OAI-SearchBot, omgilibot, PerplexityBot, PiplBot Blocking No — crawling allowed
# www.garmin.com
# Exceptions for all user agents:
User-agent: *
Disallow: /products/comparison.jsp
Disallow: /dealerResource/*
Disallow: /lbt/*
Disallow: /account/
Allow: /account/$

# Sitemaps
Sitemap: https://www.garmin.com/www-sitemaps-index.xml
Sitemap: https://www.garmin.com/sitemap-index-blogs.xml
Sitemap: https://www.garmin.com/product-sitemap-index.xml
Sitemap: https://www.garmin.com/category-sitemap-index.xml

# Individual user agent settings:
User-agent: gsa-garmin
Allow: /

User-agent: anthropic-ai
User-agent: CCBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: cohere-ai
User-agent: DuckAssistBot
User-agent: GPTBot
User-agent: Meta-ExternalAgent
User-agent: OAI-SearchBot
User-agent: Quora-Bot
Allow: /*/c/*
Allow: /*/p/*
Disallow: /

# Disallowed user agents:
User-agent: Better Uptime Bot
User-agent: DataForSeoBot
User-agent: ecoresearchCrawler
User-agent: EyeMonIT Uptime Bot
User-agent: omgili
User-agent: omgilibot
User-agent: PerplexityBot
User-agent: PiplBot
User-agent: TurnitinBot
User-agent: UptimeRobot
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 65 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.garmin.com/
301https://garmin.com/

Preferred variant: www

HTTP → HTTPS

301http://www.garmin.com/ → https://www.garmin.com/

Consistent

A+
Domain Intelligence
garmin.com — via MarkMonitor Inc., 31 years, 4 months old, hosted on Cloudflare
PASS
garmin.com — via MarkMonitor Inc., 31 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until May 3, 2028 (2 years, 1 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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

625 days

May 3, 2028

SSL certificate

75 days

Issued by Google Trust Services

Domain age

31 years, 4 months

Registered May 2, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.138.86

Registrar

MarkMonitor Inc.

Lock status unknown 6 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
Registrar MarkMonitor Inc.
Created May 2, 1995 (31 years, 4 months ago)
Expires May 3, 2028 (2 years, 1 months)
Last Updated April 1, 2026
Name Servers a1-59.akam.net, a12-66.akam.net, a18-67.akam.net, a3-64.akam.net, a6-65.akam.net, a9-66.akam.net
DNSSEC Not enabled
Hosting
IP Address 162.159.138.86
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.6s)

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

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

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 7 ms Server Processing 18 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