Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
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 & Recommendations88 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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 & DeliveryCloudflare (BYPASS)REVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 44 ms lookupPASS
| A | 104.20.40.87, 172.66.153.234 |
| AAAA | 2606:4700:10::ac42:99ea, 2606:4700:10::6814:2857 |
| CNAME | — |
| NS | noel.ns.cloudflare.com, iris.ns.cloudflare.com |
| MX | 10 mx01.schalke04.de 20 mforward.dtag.de |
| TXT | facebook-domain-verification=rt74f2g9ugo2vdwxr5ujpm8o3a5svv ns.udag.net. hostmaster.united-domains.de 2017121901 00D1x0000000MVy=1TB9K0000000VAH google-site-verification=wf8INi4HMactEgffQYH6jo2-uelLv4-fBhFfHD7B0ik google-site-verification=TXfRkz-kLk8iFBK3xy9Y_RCy3NYD0vR1VQ9D5x_YVKA google-site-verification=yiotsynVQ_NlOmTIzlA4GL9KZeBtQwIjdgILGuipdB0 apple-domain-verification=aNMdyD1ja1eZeneh MS=ms17506156 _globalsign-domain-verification=6AFCpDybJa_TfSfZ78ggwl025E_gy5OoqUpgFA4XzW MS=ms80176648 google-site-verification=8SnTuZ7utt00e3hHjWsSGEWN5766h2iUW4m1d7gDcQQ cisco-ci-domain-verification=882d7b9bd873628dc2208c1988de5b5a21572a4b7ecebde337c... SPF v=spf1 mx include:spf.mailjet.com include:aspmx.pardot.com include:_spf.salesfor... rZZZRH6smdfnd0BhzxztYysKfhMz9wcWyhvwQ18R9flFytnUWXfORim8ecv0eRBUz6IVhPtCBk40JjLL... 0367BD625F518442EC1755A2D04A3DA4B852D616 MS=ms76559451 |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 21ms across 3 resolvers (spread 10ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://schalke04.de
103 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://schalke04.de | 200 | 103 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceschalke04.dePASS
Unknown
88 days
Issued by Let's Encrypt
Unknown
Status unknown
Protects against DNS spoofing
Unknown
2606:4700:10::6814:2857
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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