Infrastructure
· 17 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.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/3 IPs match cert SANREVIEW
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
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 & Recommendations59 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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records3 A records, 41 ms lookupPASS
| A | 3.224.19.154, 32.199.147.76, 52.72.216.140 |
| AAAA | — |
| CNAME | — |
| NS | dns1.p05.nsone.net, dns3.p05.nsone.net, dns2.p05.nsone.net, dns4.p05.nsone.net |
| MX | 10 mxb-00a17301.gslb.pphosted.com 10 mxa-00a17301.gslb.pphosted.com 20 mx0a-00a17301.pphosted.com 20 mx0b-00a17301.pphosted.com |
| TXT | smartsheet-site-validation=oMy2hiSOxZp9S8vm9DKkUPKNqqB0ufdZ google-site-verification=9cB8liQRQb28dQBqxzTce9QxKrQ-i49TaUC1gb9hDZE ZOOM_verify_xWhArnaoktgfC9TPnJyepZ inbound adobe-idp-site-verification=d266b426130588069c9d5b76db345b36532058a66f36380fe985... facebook-domain-verification=wuce6e5xzen63kvin0wnezovdrsx64 _00z279402xehowo4mbv2r2qi42l9tyg google-site-verification=6CESE_rGuHHElgUcDrWhTikFRYmAa9UxkS8l-7DHXp8 google-site-verification=5L_AJnC2bIXTvxGA7YN8mWF736oIS25va0YgjoMMl8o _lq9l7q95inxvwkxmxp9tm04ee47nw3u _1h4qah587e8c66rkz1bw624l2gu9nn1 google-site-verification=sgPd3o6avBeNjQQHck1SdY9T9tCIpY7uuTEKgrjSUzI Verification Token=056br29gq2n3bxrrgnycn5gl5t7x84gv yahoo-verification-key=ASAGciLz+ZkbF3NlmI5cq6bGG3Dke7+mxOSR9CmHTus= google-site-verification=MwlAu7EQcQ0wfEXmAg1AQ7jPjZA-obI23zD_6t70cOA cursor-domain-verification-3smzbv=BtSKIbSN5gsLoFMzwFlfLmHxz _7zwim549e9t4hdm5b38khfp9ua3ar2b dropbox-domain-verification=201yvjsfrkv5 SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:amazonses.com ~all MS=ms58192621 |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 22ms across 3 resolvers (spread 9ms)PASS
ARedirect Chain1 redirect(s), 316 ms totalPASS
https://cnbc.com
298 ms · HTTP/1.1
https://www.cnbc.com
18 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cnbc.com | 301 | 298 ms | HTTP/1.1 | |
| 2 | https://www.cnbc.com | 403 | 18 ms | HTTP/1.1 | AkamaiGHost |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecnbc.com — via MarkMonitor Inc., 29 years, 2 months old, hosted on AWSPASS
442 days
September 29, 2027
59 days
Issued by Amazon
29 years, 2 months
Registered September 30, 1997
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.72.216.140
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice