Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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: /ceapi
Disallow: /quickselect
Disallow: /jumplist
User-agent: Slurp
Crawl-delay: 2
User-agent: Mediapartners-Google
Disallow:
User-agent: wget
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-SearchBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: magpie-crawler
Disallow: /
User-agent: bingbot
Allow: /
Crawl-delay: 3
User-agent: PerplexityBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Omgilibot
Disallow: /
User-agent: Omgilibot
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: SirdataBot
Disallow: /
User-agent: LCC
Disallow: /
User-agent: TurnitinBot
Disallow: /
User-agent: dotbot
Disallow: /
User-agent: proximic
Disallow: /
User-agent: ecoresearchCrawler/0.9
Disallow: /
User-agent: ecoresearchCrawler
Disallow: /
User-agent: Clickagy Intelligence Bot
Disallow: /
User-agent: Clickagy Intelligence Bot v2
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: Perplexity-User
Disallow: /
User-agent: Deepseek
Disallow: /
User-agent: DeepseekBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: *
Allow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations78 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
ADNS Records4 A records, 28 ms lookupPASS
| A | 143.204.55.99, 143.204.55.82, 143.204.55.40, 143.204.55.71 |
| AAAA | 2600:9000:20a5:8600:1f:fb94:3440:93a1, 2600:9000:20a5:c400:1f:fb94:3440:93a1, 2600:9000:20a5:e600:1f:fb94:3440:93a1, 2600:9000:20a5:7800:1f:fb94:3440:93a1, 2600:9000:20a5:7200:1f:fb94:3440:93a1, 2600:9000:20a5:a000:1f:fb94:3440:93a1, 2600:9000:20a5:f800:1f:fb94:3440:93a1, 2600:9000:20a5:f000:1f:fb94:3440:93a1 |
| CNAME | d3a76sutnekbf5.cloudfront.net |
| NS | ns-778.awsdns-33.net, ns-1078.awsdns-06.org, ns-487.awsdns-60.com, ns-1756.awsdns-27.co.uk |
| 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)
A+Redirect ChainNo redirects — direct accessPASS
https://www.transfermarkt.com
108 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.transfermarkt.com | 200 | 108 ms | HTTP/1.1 | nginx |
A+IPv6 ReadinessIPv6 reachable (31 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencetransfermarkt.com — via InterNetX GmbH, 25 years, 7 months old, hosted on TLN-AS, DEPASS
196 days
December 28, 2026
78 days
Issued by Let's Encrypt
25 years, 7 months
Registered December 28, 2000
Not enabled
Protects against DNS spoofing
TLN-AS, DE
ASN AS59507
5.159.57.195
InterNetX GmbH
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