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.
CCrawlabilityActionrobots.txt present, sitemap with 3 URLsREVIEW
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
User-agent: Yandex
Disallow: /
User-agent: *
Disallow: /
Allow: /$
Allow: /devices$
Allow: /devices/$
Allow: /devices/index.html$
Allow: /sitemap.xml
Allow: /legal-notice
Allow: /terms
Allow: /about
Host: www.myfritz.net
Sitemap: https://www.myfritz.net/sitemap.xml
BTLS Certificate Expiry & Recommendations273 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
A+DNS Records1 A records, 43 ms lookupPASS
| A | 212.42.244.100 |
| AAAA | 2001:bf0:244:244::100 |
| CNAME | — |
| NS | ns2.myfritz.net, ns3.myfritz.net, ns1.myfritz.net |
| MX | 5 mail1.myfritz.net 5 mail2.myfritz.net |
| TXT | google-site-verification=EweYOrTvD0SidAfgtzGITmZ7yleKW6-8HsgZYyl5VOU SPF v=spf1 ip4:212.42.244.0/24 ip6:2001:bf0:244::/48 ~all 6tcdx31mg1py8nznkdy5byx5389fw9kf nm42qvg40mc8fd48l3p1cp0mmvjgd5fm cea301c97f144dfd932cfdc82f84c640 kkn3zz63w66gh8npqqbzqzq9qtm1ltyf https://github.com/publicsuffix/list/pull/77 |
| 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.
ARedirect Chain1 redirect(s), 275 ms totalPASS
https://myfritz.net
115 ms · HTTP/1.1
https://www.myfritz.net/devices/
160 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://myfritz.net | 302 | 115 ms | HTTP/1.1 | |
| 2 | https://www.myfritz.net/devices/ | 200 | 160 ms | HTTP/1.1 | cloud-gateway/cloud-gateway-4.6.56 (AVM) |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+IPv6 ReadinessIPv6 reachable (36 ms)PASS
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencemyfritz.net — via InterNetX GmbH, 14 years, 9 months oldPASS
71 days
September 22, 2026
273 days
Issued by DigiCert Inc
14 years, 9 months
Registered September 22, 2011
Not enabled
Protects against DNS spoofing
Unknown
2001:bf0:244:244::100
InterNetX GmbH
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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