Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations84 days until leaf cert expires — 3 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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryVercelREVIEW
ADNS Records2 A records, 22 ms lookupPASS
| A | 66.33.60.67, 76.76.21.98 |
| AAAA | — |
| CNAME | cname.vercel-dns.com |
| NS | ns1.vercel-dns-3.com, ns4.vercel-dns-3.com, ns3.vercel-dns-3.com, ns2.vercel-dns-3.com |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
ARedirect Chain1 redirect(s), 246 ms totalPASS
https://www.neon.tech
77 ms · HTTP/1.1
https://neon.com/
169 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.neon.tech | 308 | 77 ms | HTTP/1.1 | Vercel |
| 2 | https://neon.com/ | 200 | 169 ms | HTTP/1.1 | Vercel |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
# *
User-agent: *
Disallow: /home$
Disallow: /docs/auth/legacy/
# Host
Host: https://neon.com
# Sitemaps
Sitemap: https://neon.com/sitemap.xml
Sitemap: https://neon.com/blog-sitemap.xml
Sitemap: https://neon.com/sitemap-postgres.xml
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceneon.tech — via MarkMonitor Inc., 4 years oldPASS
634 days
April 6, 2028
84 days
Issued by Let's Encrypt
4 years
Registered April 6, 2022
Enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:1733
MarkMonitor Inc.