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 & Recommendations40 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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 Records2 A records, 50 ms lookupPASS
| A | 104.18.2.81, 104.18.3.81 |
| AAAA | 2606:4700::6812:251, 2606:4700::6812:351 |
| CNAME | — |
| NS | eva.ns.cloudflare.com, huxley.ns.cloudflare.com |
| MX | 1 smtp.google.com |
| TXT | 1password-site-verification=BTAS7KDWFVE3PIX27YOMCEA4UM _4fd17hf9g4w6weyl7b89d50op01uuwy _wtcvpslab3g32q1k3qlm43oi6l2j6jz anthropic-domain-verification-av5df3=eJI0OpFMGof3X63foE3SYX8WB apple-domain-verification=tlzNYi4TiyIyqRev atlassian-domain-verification=N5zXaaBRBE9Cd5PSTyhBKk9XTXQUL2ST8oiy1waAi9MQDBeuFX... cursor-domain-verification-wvr4wa=YVZgu4ALlb9yhXagFAxdhFGro google-site-verification=6lIAZ--o60UH9A-Plhu-Oy86l7upix6tiJXoVgEEA3w google-site-verification=CHkHcMqh2XpsTbqD1FJkIg4_4UXBaMpt28V_1M2gOoA linear-domain-verification=5rhfaqatrhjp miro-verification=05b393eebea8904ac08432f96b3bb4895912712c openai-domain-verification=dv-MSTq1JYFRC7keX9UmL6TR71z slack-domain-verification=PY2dIaxRPOTm3mF4P2MTsIfMOxSswIjH1h9iuBFW stripe-verification=1F2809F519F0B98761070B7CC47045D31D9A42DF106EF4D9F766B2FC7FF8... stripe-verification=20C45907E223438E06807BD33445C8684B2C0D32C7ADB89FE604D047D11B... stripe-verification=CFF2AB5286BB7E6BE71F0EAC382DB65EAD5933CC134963F09AE29F6EA5B0... SPF v=spf1 include:_spf.google.com include:helpscoutemail.com include:servers.mcsv.n... |
| 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://laravel.com
58 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://laravel.com | 200 | 58 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 634 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: /cdn-cgi/
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencelaravel.com — via NameCheap, Inc., 15 years, 3 months old, hosted on CloudflarePASS
1737 days
March 16, 2031
40 days
Issued by Google Trust Services
15 years, 3 months
Registered March 16, 2011
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.2.81
NameCheap, Inc.
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