Skip to content
https://reactjs.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
5 PASS 4 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 33 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 33 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /version/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
54 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

54
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
B
CDN & Delivery
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::x5v5x-1776814754257-68a28d42e33b
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::x5v5x-1776814754257-68a28d42e33b
A+
DNS Records
1 A records, 44 ms lookup
PASS
1 A records, 44 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 76.76.21.21
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: rohin.ns.cloudflare.com, joan.ns.cloudflare.com
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::
SPF record present in TXT
Info::
DNS resolution time: 44 ms
Got: 44 ms
A76.76.21.21
AAAA
CNAME
NSrohin.ns.cloudflare.com, joan.ns.cloudflare.com
MX
TXT
SPF v=spf1 include:spf.mandrillapp.com include:sparkpostmail.com ~all
google-site-verification=8cSSWOK5msv3tzIFqXSvcb-KzSdG_E9g_H0bLIKhcWE
google-site-verification=phixj4WdeUCjzqWQjOkCLkD8y6oeiJbqnCihojcYOWA
CAALookup not available with standard resolver
Resolved in 44 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.

A
Redirect Chain
1 redirect(s), 199 ms total
PASS
1 redirect(s), 199 ms total
Info::
Single redirect
Got: https://reactjs.org → https://react.dev/ (308)
Info::
Cross-domain redirect detected

https://reactjs.org

91 ms · HTTP/1.1

308

https://react.dev/

108 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://reactjs.org30891 msHTTP/1.1Vercel
2https://react.dev/200108 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

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.reactjs.org/
200https://reactjs.org/

HTTP → HTTPS

308http://reactjs.org/ https://reactjs.org/

Use 301 (permanent) instead of 302 (temporary)

A
Domain Intelligence
reactjs.org — via RegistrarSEC LLC, 13 years, 1 months old, hosted on AWS
PASS
reactjs.org — via RegistrarSEC LLC, 13 years, 1 months old, hosted on AWS
Warning::
Domain expires in 37 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 29, 2026
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: RegistrarSEC LLC
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

EXPIRED

May 29, 2026

SSL certificate

54 days

Issued by Let's Encrypt

Domain age

13 years, 1 months

Registered May 29, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

RegistrarSEC LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RegistrarSEC LLC
Created May 29, 2013 (13 years, 1 months ago)
Expires May 29, 2026 (1 months)
Last Updated March 6, 2025
Name Servers joan.ns.cloudflare.com, rohin.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 42 ms TCP Connect 1 ms TLS Handshake 45 ms Server Processing 27 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