Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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
A sitemap helps search engines discover and index your pages more efficiently.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations82 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
A+DNS Records1 A records, 32 ms lookupPASS
| A | 199.36.158.100 |
| AAAA | 2620:0:890::100 |
| CNAME | — |
| NS | ns4.googledomains.com, ns3.googledomains.com, ns1.googledomains.com, ns2.googledomains.com |
| MX | 0 smtp.google.com |
| TXT | dashboard.flutter.devgoogle-site-verification=zJs_c6I-QYsjp6txdbnViGf2jC2rt6tGIL... flutter.devgoogle-site-verification=4Rvc1mRi0OUczPHAfReCQF3vpN4g0c3MhoMCfPIA4lA flutter.devgoogle-site-verification=EZ_oZwPsj3nJyq2Wyxm_df2syuPDWZWXcmMnIqSJmoc flutter.devgoogle-site-verification=8vH-ImHAcuHDyYpsU2xjqH98WmQOYnpuZ7qLMQKSfe0 flutter.devgoogle-site-verification=ynwJ9uOJaXAo0h8elDzD-ol7A9qib6IMafu8WLbb8GM flutter.devgoogle-site-verification=iib-jo_2OjcBLBlgoQBU_Hqpg7jRbUGEAGI55A6ZTok SPF v=spf1 -all flutter.devgoogle-site-verification=lIqguczSC2ik6Gpj63wvAeEZS5AV_1i9yz9Qlrndp-4 flutter.devgoogle-site-verification=34Rg6emh5D_Ea_zMqCFpkYgvqXmLxiVWcyw6M92vamo flutter.devgoogle-site-verification=qofi_7lIOmqtdpsEl6ssQkegqADxW7CjrRZdoc_9GWw download.flutter.devgoogle-site-verification=AeYMn1LTlmz1OT8omXL-buaYssgGkQIrAtd... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect ChainNo redirects — direct accessPASS
https://flutter.dev
8 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://flutter.dev | 200 | 8 ms | HTTP/1.1 |
A+IPv6 ReadinessIPv6 reachable (0 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceflutter.dev — via MarkMonitor Inc., 7 years, 4 months oldPASS
184 days
January 11, 2027
82 days
Issued by Google Trust Services
7 years, 4 months
Registered January 11, 2019
Not enabled
Protects against DNS spoofing
Unknown
2620:0:890::100
MarkMonitor 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