Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BTLS Certificate Expiry & Recommendations33 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryNetlifyREVIEW
A+DNS Records2 A records, 73 ms lookupPASS
| A | 52.52.192.191, 13.52.188.95 |
| AAAA | 2600:1f1c:446:4900::258, 2600:1f1c:446:4900::259 |
| CNAME | — |
| NS | edna.ns.cloudflare.com, norm.ns.cloudflare.com |
| MX | — |
| TXT | d825ad654c5348cb9f35e31d66f5244a SPF v=spf1 a -all |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect ChainNo redirects — direct accessPASS
https://reactnative.dev
54 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://reactnative.dev | 200 | 54 ms | HTTP/1.1 | Netlify |
A+Crawlabilityrobots.txt present, sitemap with 1921 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow:
- https://reactnative.dev/blog
- https://reactnative.dev/blog/2015/03/26/react-native-bringing-modern-web-techniques-to-mobile
- https://reactnative.dev/blog/2015/09/14/react-native-for-android
- https://reactnative.dev/blog/2015/11/23/making-react-native-apps-accessible
- https://reactnative.dev/blog/2016/03/24/introducing-hot-reloading
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencereactnative.dev — via RegistrarSEC, LLC, 7 years, 2 months old, hosted on AWSPASS
249 days
February 19, 2027
33 days
Issued by Let's Encrypt
7 years, 2 months
Registered February 19, 2019
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.52.192.191
RegistrarSEC, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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