Skip to content
https://nextjs.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 6 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 216.230.84.129: lookup 216.230.84.129: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 216.230.86.1: lookup 216.230.86.1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
42 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 29 ms lookup
PASS
2 A records, 29 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 216.230.84.129, 216.230.86.1
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.vercel-dns.com, ns1.vercel-dns.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 29 ms
Got: 29 ms
A216.230.84.129, 216.230.86.1
AAAA—
CNAME—
NSns2.vercel-dns.com, ns1.vercel-dns.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=h7m7xPSl46-ALWigMUJfFFOFZjKe3jZECHyXSomzXvM
google-site-verification=roTfUbzRkjTgiiXb6Lbsh2sQyaAlS_sN32t5nMz8kTQ
google-site-verification=BsXDDAvxM3KYqCMD-vaPIxduP9YLqllhaBlERyhjsgw
SPF v=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net ~al...
google-site-verification=VUelRm0rDJ9Mxpi3RYfJ0M_Qqbxyo8mSYdn0grLEFIU
CAALookup not available with standard resolver
Resolved in 29 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: letsencrypt.org, pki.goog, sectigo.com
PASS
issue: letsencrypt.org, pki.goog, sectigo.com
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org, pki.goog, sectigo.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 18ms across 3 resolvers (spread 5ms)
PASS
Mean 18ms across 3 resolvers (spread 5ms)
Info::
Quad9: 16ms
Got: 16ms via 9.9.9.9:53
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 21ms
Got: 21ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://nextjs.org

https://nextjs.org

80 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nextjs.org20080 msHTTP/1.1Vercel
A
Crawlability
no robots.txt, sitemap with 661 URLs
PASS
no robots.txt, sitemap with 661 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 661 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.

sitemap.xml 200 OK
Type URL Set URLs 661 entries Valid XML Yes
Sample URLs:
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, 8 months old, hosted on AWS
PASS
nextjs.org — via Tucows Domains Inc., 9 years, 8 months old, hosted on AWS
Info::
Domain registered until Oct 3, 2035 (9 years, 6 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.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

3425 days

October 3, 2035

SSL certificate

42 days

Issued by Let's Encrypt

Domain age

9 years, 8 months

Registered October 3, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.230.86.1

Registrar

Tucows Domains Inc.

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created October 3, 2016 (9 years, 8 months ago)
Expires October 3, 2035 (9 years, 6 months)
Last Updated April 23, 2026
Name Servers ns1.vercel-dns.com, ns2.vercel-dns.com
DNSSEC Not enabled
Hosting
IP Address 216.230.86.1
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 148 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 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.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
134 ms
Total Time Total request time from DNS lookup through full response.
149 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 1 ms TLS Handshake 36 ms Server Processing 68 ms Content Transfer 14 ms
A+
CDN & Delivery
Vercel (HIT)
PASS
Vercel (HIT)
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::cle1::ksp9n-1778270080348-794677cfe3fd
Info::
CDN cache status: HIT
CDN Detected: Vercel
Provider Vercel Cache Status HIT Evidence x-vercel-id: cdg1::cle1::ksp9n-1778270080348-794677cfe3fd
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=235, x-vercel-cache=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback