Skip to content
https://dev.to

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
7 PASS 2 REVIEW
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
252 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
4 A records, 5046 ms lookup
PASS
4 A records, 5046 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.194.217, 151.101.130.217, 151.101.66.217, 151.101.2.217
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: jill.ns.cloudflare.com, josh.ns.cloudflare.com
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
Warning::
DNS resolution is slow (5046 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 5046 ms
A151.101.194.217, 151.101.130.217, 151.101.66.217, 151.101.2.217
AAAA—
CNAME—
NSjill.ns.cloudflare.com, josh.ns.cloudflare.com
MX
1 smtp.google.com
TXT
google-site-verification=UxVw159V9puXGvEI2bXj26vXxYpAuLeKQIdd34ZxJhc
SPF v=spf1 a mx include:_spf.google.com include:sendgrid.net include:servers.mcsv.ne...
_globalsign-domain-verification=VzRovTWhxjedMqXFfoiZ-UNRnlnuTXYHgjKemPNt33
facebook-domain-verification=1xzy1qk89qs7ngxdt5e4s0kvvqw701
google-site-verification=oTtYzW83zP_41DlUrb_VXtAjLTW1p71RBmWR2g5ctrk
google-site-verification=RCxAYvXUKM7ssPUkw0ye4xW51pN1G-ZNaaFiI2s5rdQ
CAALookup not available with standard resolver
Resolved in 5046 ms

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://dev.to

https://dev.to

47 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dev.to20047 msHTTP/1.1Heroku
A+
Crawlability
robots.txt present, sitemap with 253 URLs
PASS
robots.txt present, sitemap with 253 URLs
Info::
robots.txt is present
Got: 450 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 253 entries
Info::
Sitemap index with 253 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 450 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /*/actions_panel*
Disallow: /users/auth/twitter*
Disallow: /users/auth/github*
Disallow: /report-abuse?url=*
Disallow: /connect/@*
Disallow: /search?q=*
Disallow: /search/?q=*
Disallow: /search/feed_content?*
Disallow: /listings*?q=*
Disallow: /mod/*
Disallow: /mod?*
Disallow: /admin/*
Disallow: /reactions?*
Disallow: /async_info/base_data
Disallow: /ahoy/*
Disallow: /auth_pass/*

Sitemap: https://dev.to/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 253 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.dev.to/
200https://dev.to/

Preferred variant: non-www

HTTP → HTTPS

301http://dev.to/ → https://dev.to/

Consistent

A+
Domain Intelligence
dev.to — via Government of Kingdom of Tonga, 10 years, 1 months old, hosted on Fastly
PASS
dev.to — via Government of Kingdom of Tonga, 10 years, 1 months old, hosted on Fastly
Info::
Domain registered until Apr 5, 2027 (1 years 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: Government of Kingdom of Tonga
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

293 days

April 5, 2027

SSL certificate

252 days

Issued by GlobalSign nv-sa

Domain age

10 years, 1 months

Registered April 5, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.130.217

Registrar

Government of Kingdom of Tonga

Lock status unknown 2 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 Government of Kingdom of Tonga
Created April 5, 2016 (10 years, 1 months ago)
Expires April 5, 2027 (1 years)
Last Updated April 7, 2022
Name Servers jill.ns.cloudflare.com, josh.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 151.101.130.217
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (8.0s)

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 49 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
46 ms
Total Time Total request time from DNS lookup through full response.
50 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 3 ms Content Transfer 4 ms
A+
CDN & Delivery
Fastly (HIT, HIT)
PASS
Fastly (HIT, HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-den-kden1300099-DEN, cache-sin-wsat1880038-SIN
Info::
CDN cache status: HIT, HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT Evidence x-served-by: cache-den-kden1300099-DEN, cache-sin-wsat1880038-SIN
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback