Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records4 A records, 1139 ms lookupREVIEW
| A | 180.222.114.12, 106.10.236.40, 106.10.236.37, 180.222.114.11 |
| AAAA | 2406:2000:e4:1604::1001, 2406:2000:98:800::e5, 2406:2000:98:800::e6, 2406:2000:e4:1604::1000 |
| CNAME | engadget-ycpi-media_edge.g03.yahoodns.net |
| NS | — |
| 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)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
BCrawlabilityrobots.txt present, no sitemapREVIEW
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
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: /forward
Disallow: /traffic
Disallow: /mm_track
Disallow: /tag/expire-images*
Disallow: /_remote
Disallow: /_td_api
Disallow: /_td
Disallow: /_uac/adpage.html
Disallow: /caas/
User-Agent: ADmantX
User-Agent: AlphaBot
User-Agent: anthropic-ai
User-Agent: AwarioRssBot
User-Agent: AwarioSmartBot
User-Agent: BLEXBot
User-Agent: Buzzbot
User-Agent: Bytespider
User-Agent: CCBot
User-Agent: ChatGPT-User
User-Agent: claritybot
User-Agent: Claude-Web
User-Agent: ClaudeBot
User-Agent: cohere-ai
User-Agent: Diffbot
User-Agent: FacebookBot
User-Agent: FriendlyCrawler
User-Agent: Google-Extended
User-Agent: GPTBot
User-Agent: huggingface
User-Agent: ImagesiftBot
User-Agent: img2dataset
User-Agent: magpie-crawler
User-Agent: Meltwater
User-Agent: Neevabot
User-Agent: news-please
User-Agent: NewsNow
User-Agent: Nutch
User-Agent: omgili
User-Agent: omgilibot
User-Agent: http://panscient.com
User-Agent: Perplexity-ai
User-Agent: PerplexityBot
User-Agent: PetalBot
User-Agent: PiplBot
User-Agent: http://scoop.it
User-Agent: Scrapy
User-Agent: Seekr
User-Agent: SentiBot
User-Agent: SeznamBot
User-Agent: TurnitinBot
User-Agent: YouBot
User-Agent: ZumBot
Disallow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations64 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+Redirect ChainNo redirects — direct accessPASS
https://www.engadget.com
744 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.engadget.com | 200 | 744 ms | HTTP/1.1 | ATS |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligenceengadget.com — via MarkMonitor Inc., 22 years, 6 months old, hosted on AWSPASS
195 days
January 23, 2027
64 days
Issued by DigiCert Inc
22 years, 6 months
Registered January 23, 2004
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.248.158.7
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