Skip to content
https://nextjs.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Santa Clara, United Stated
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
76 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 216.230.84.193, 216.230.84.1
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.vercel-dns.com, ns2.vercel-dns.com
Info::
5 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: 7 ms
Got: 7 ms
A216.230.84.193, 216.230.84.1
AAAA
CNAME
NSns1.vercel-dns.com, ns2.vercel-dns.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=BsXDDAvxM3KYqCMD-vaPIxduP9YLqllhaBlERyhjsgw
google-site-verification=VUelRm0rDJ9Mxpi3RYfJ0M_Qqbxyo8mSYdn0grLEFIU
google-site-verification=h7m7xPSl46-ALWigMUJfFFOFZjKe3jZECHyXSomzXvM
google-site-verification=roTfUbzRkjTgiiXb6Lbsh2sQyaAlS_sN32t5nMz8kTQ
SPF v=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net ~al...
CAALookup not available with standard resolver
Resolved in 7 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.

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

https://nextjs.org

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nextjs.org20061 msHTTP/1.1Vercel
A
Crawlability
no robots.txt, sitemap with 654 URLs
PASS
no robots.txt, sitemap with 654 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 654 entries

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

307https://www.nextjs.org/
200https://nextjs.org/

HTTP → HTTPS

308http://nextjs.org/ https://nextjs.org/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
nextjs.org — via Tucows Domains Inc., 9 years, 7 months old, hosted on AWS
PASS
nextjs.org — via Tucows Domains Inc., 9 years, 7 months old, hosted on AWS
Info::
Domain registered until Oct 3, 2035 (9 years, 7 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: Tucows Domains Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

3369 days

October 3, 2035

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

9 years, 7 months

Registered October 3, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.230.86.65

Registrar

Tucows Domains Inc.

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 Tucows Domains Inc.
Created October 3, 2016 (9 years, 7 months ago)
Expires October 3, 2035 (9 years, 7 months)
Last Updated February 2, 2026
Name Servers ns1.vercel-dns.com, ns2.vercel-dns.com
DNSSEC Not enabled
Hosting
IP Address 216.230.86.65
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 8 ms TCP Connect 3 ms TLS Handshake 11 ms Server Processing 167 ms Content Transfer 9 ms
A+
CDN & Delivery
Vercel (HIT)
PASS
Vercel (HIT)
Info::
Site is served via Vercel CDN
Got: x-vercel-id: sfo1::pdx1::ltzdr-1775320973134-f3bdad301a15
Info::
CDN cache status: HIT
CDN Detected: Vercel
Provider Vercel Cache Status HIT Evidence x-vercel-id: sfo1::pdx1::ltzdr-1775320973134-f3bdad301a15
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback