Skip to content
https://www.snyk.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
4
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW
B
DNS Records
1 A records, 34 ms lookup
REVIEW
1 A records, 34 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.10.72.103
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0:495::ecd, 2a02:26f0:e0:483::ecd
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: snyk.io.edgekey.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: 34 ms
Got: 34 ms
A23.10.72.103
AAAA2a02:26f0:e0:495::ecd, 2a02:26f0:e0:483::ecd
CNAMEsnyk.io.edgekey.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 34 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

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
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.snyk.io/
200https://snyk.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.snyk.io/ → https://snyk.io/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A
Redirect Chain
1 redirect(s), 157 ms total
PASS
1 redirect(s), 157 ms total
Info::
Single redirect
Got: https://www.snyk.io → https://snyk.io/ (301)
Info::
WWW normalization redirect

https://www.snyk.io

10 ms · HTTP/1.1

301

https://snyk.io/

148 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.snyk.io30110 msHTTP/1.1AkamaiGHost
2https://snyk.io/200148 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0:495::ecd, 2a02:26f0:e0:483::ecd
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0:495::ecd, 2a02:26f0:e0:483::ecd Connection Reachable (0 ms)
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 965 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 965 B Sitemaps referenced 13 User-agents * Blocking No — crawling allowed
# *
User-agent: *
Allow: /

# *
User-agent: *
Disallow: /*.json$
Disallow: /*_buildManifest.js$
Disallow: /*_middlewareManifest.js$
Disallow: /*_ssgManifest.js$
Disallow: /*.js$

# *
User-agent: *
Disallow: /advisor

# Host
Host: https://snyk.io

# Sitemaps
Sitemap: https://snyk.io/sitemap-index.xml
Sitemap: https://snyk.io/sitemaps/sitemap-pages.xml
Sitemap: https://snyk.io/sitemaps/sitemap-articles.xml
Sitemap: https://snyk.io/sitemaps/sitemap-blogs.xml
Sitemap: https://snyk.io/sitemaps/sitemap-case-studies.xml
Sitemap: https://snyk.io/sitemaps/sitemap-contributors.xml
Sitemap: https://snyk.io/sitemaps/sitemap-events.xml
Sitemap: https://snyk.io/sitemaps/sitemap-podcasts.xml
Sitemap: https://snyk.io/sitemaps/sitemap-policies.xml
Sitemap: https://snyk.io/sitemaps/sitemap-press-releases.xml
Sitemap: https://snyk.io/sitemaps/sitemap-videos.xml
Sitemap: https://snyk.io/sitemaps/sitemap-misc.xml
Sitemap: https://snyk.io/advisor/sitemap/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 12 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 73 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
52 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.
16 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
74 ms
Total Time Total request time from DNS lookup through full response.
74 ms

Connection waterfall

DNS Lookup 52 ms TCP Connect 1 ms TLS Handshake 16 ms Server Processing 4 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback