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

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 Madrid, Spain
301 Moved Permanently
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.

B
Redirect Chain
2 redirect(s), 368 ms total
REVIEW
2 redirect(s), 368 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://sentry.io:443/

https://www.sentry.io

58 ms · HTTP/1.1

301

https://sentry.io:443/

186 ms · HTTP/1.1

302

https://sentry.io:443/welcome/

124 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.sentry.io30158 msHTTP/1.1
2https://sentry.io:443/302186 msHTTP/1.1nginx
3https://sentry.io:443/welcome/200124 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
43 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

43
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, 24 ms lookup
PASS
1 A records, 24 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.160.100.224
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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: 24 ms
Got: 24 ms
A34.160.100.224
AAAA
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 24 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.

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)

A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 85 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 85 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /api/
Allow: /

Sitemap: https://sentry.io/sitemap-index.xml

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.sentry.io/
302https://sentry.io/

Preferred variant: www

HTTP → HTTPS

301http://www.sentry.io/ https://www.sentry.io:443/

Consistent

A+
Domain Intelligence
sentry.io — via Gandi SAS, 14 years, 2 months old, hosted on Google Cloud
PASS
sentry.io — via Gandi SAS, 14 years, 2 months old, hosted on Google Cloud
Info::
Domain registered until Apr 7, 2027 (1 years remaining)
Info::
Registrar: Gandi SAS
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

233 days

April 7, 2027

SSL certificate

43 days

Issued by Let's Encrypt

Domain age

14 years, 2 months

Registered April 7, 2012

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

35.186.247.156

Registrar

Gandi SAS

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Gandi SAS
Created April 7, 2012 (14 years, 2 months ago)
Expires April 7, 2027 (1 years)
Last Updated March 12, 2026
Name Servers ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
Registrant Functional Software, Inc dba Sentry
Hosting
IP Address 35.186.247.156
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (1.5s)
A+
HTTP Probe Timing
Total 74 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
18 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
21 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.
75 ms

Connection waterfall

DNS Lookup 18 ms TCP Connect 17 ms TLS Handshake 21 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