Skip to content
https://nuxt.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
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
70 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
1 A records, 1704 ms lookup
PASS
1 A records, 1704 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.150.1.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: tessa.ns.cloudflare.com, jaxson.ns.cloudflare.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
Warning::
DNS resolution is slow (1704 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1704 ms
A216.150.1.1
AAAA
CNAME
NStessa.ns.cloudflare.com, jaxson.ns.cloudflare.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=t-ExgMp4QNprmF0N_CCWbMK39indj3XZ4ZJmddvHXhc
SPF v=spf1 include:spf.mailjet.com ?all
google-site-verification=COJg1dK0BGs4S0hvXP7LvCK9nqJcwfgsaQ5v4Up8J7w
CAALookup not available with standard resolver
Resolved in 1704 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.

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://nuxt.com

https://nuxt.com

220 ms · HTTP/1.1 FINAL

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

308https://www.nuxt.com/
200https://nuxt.com/

HTTP → HTTPS

308http://nuxt.com/ https://nuxt.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
nuxt.com — via Cloudflare, Inc., 22 years, 7 months old, hosted on AWS
PASS
nuxt.com — via Cloudflare, Inc., 22 years, 7 months old, hosted on AWS
Info::
Domain registered until Dec 4, 2026 (8 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: Cloudflare, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

190 days

December 4, 2026

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

22 years, 7 months

Registered December 4, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.150.1.1

Registrar

Cloudflare, 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 Cloudflare, Inc.
Created December 4, 2003 (22 years, 7 months ago)
Expires December 4, 2026 (8 months)
Last Updated December 6, 2024
Name Servers jaxson.ns.cloudflare.com, tessa.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 216.150.1.1
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.4s)

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

Connection waterfall

DNS Lookup 73 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 12 ms Content Transfer 3 ms
A+
CDN & Delivery
Vercel (HIT)
PASS
Vercel (HIT)
Info::
Site is served via Vercel CDN
Got: x-vercel-id: sin1::26ljt-1775321063218-e4afe68e3646
Info::
CDN cache status: HIT
CDN Detected: Vercel
Provider Vercel Cache Status HIT Evidence x-vercel-id: sin1::26ljt-1775321063218-e4afe68e3646
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback