mz-web.de

Checked 21 October 2026, 23:31 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 0 failed 7 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

christina.ns.cloudflare.com, fred.ns.cloudflare.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
christina.ns.cloudflare.com, fred.ns.cloudflare.com
NS in the zone
christina.ns.cloudflare.com, fred.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
christina.ns.cloudflare.com162.159.38.193 172.64.34.193 108.162.194.193 2803:f800:50::6ca2:c2c1 2a06:98c1:50::ac40:22c1 2606:4700:50::a29f:26c1AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
fred.ns.cloudflare.com108.162.193.113 173.245.59.113 172.64.33.113 2a06:98c1:50::ac40:2171 2803:f800:50::6ca2:c171 2606:4700:58::adf5:3b71AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: christina.ns.cloudflare.com, fred.ns.cloudflare.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
christina.ns.cloudflare.com 162.159.38.193NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
christina.ns.cloudflare.com 172.64.34.193NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
christina.ns.cloudflare.com 108.162.194.193NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
christina.ns.cloudflare.com 2803:f800:50::6ca2:c2c1NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
christina.ns.cloudflare.com 2a06:98c1:50::ac40:22c1NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
christina.ns.cloudflare.com 2606:4700:50::a29f:26c1NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
fred.ns.cloudflare.com 108.162.193.113NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
fred.ns.cloudflare.com 173.245.59.113NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
fred.ns.cloudflare.com 172.64.33.113NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
fred.ns.cloudflare.com 2a06:98c1:50::ac40:2171NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
fred.ns.cloudflare.com 2803:f800:50::6ca2:c171NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
fred.ns.cloudflare.com 2606:4700:58::adf5:3b71NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: christina.ns.cloudflare.com: "2026.10.2"; fred.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2416705309 · primary christina.ns.cloudflare.com

Found

Primary (MNAME)
christina.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2416705309
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
christina.ns.cloudflare.com (162.159.38.193)2416705309
christina.ns.cloudflare.com (172.64.34.193)2416705309
christina.ns.cloudflare.com (108.162.194.193)2416705309
christina.ns.cloudflare.com (2803:f800:50::6ca2:c2c1)2416705309
christina.ns.cloudflare.com (2a06:98c1:50::ac40:22c1)2416705309
christina.ns.cloudflare.com (2606:4700:50::a29f:26c1)2416705309
fred.ns.cloudflare.com (108.162.193.113)2416705309
fred.ns.cloudflare.com (173.245.59.113)2416705309
fred.ns.cloudflare.com (172.64.33.113)2416705309
fred.ns.cloudflare.com (2a06:98c1:50::ac40:2171)2416705309
fred.ns.cloudflare.com (2803:f800:50::6ca2:c171)2416705309
fred.ns.cloudflare.com (2606:4700:58::adf5:3b71)2416705309

Checks

  • ✓ Serial 2416705309 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver christina.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2416705309 is a Unix timestamp (2046-08-01 03:01 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

17 records at the apex

Found

Read from
162.159.38.193:53
TypeValueTTL
SOAchristina.ns.cloudflare.com. dns.cloudflare.com. 2416705309 10000 2400 604800 18001800
NSchristina.ns.cloudflare.com.86400
NSfred.ns.cloudflare.com.86400
A104.21.81.50300
A172.67.156.249300
AAAA2606:4700:3037::6815:5132300
AAAA2606:4700:3033::ac43:9cf9300
MX10 mzweb-de0e.mail.protection.outlook.com.3600
TXT"Domain Validation for CEOS1603153806 - Auth-Code: K15WOP46"300
TXT"Domain" "Validation" "for" "CEOS1603153806" "-" "Auth-Code:" "K15WOP46"300
TXT"MS=ms74633581"300
TXT"QJB0K12niXH7uGTuCAuw3JGyzRArjtYb329WEjgCjbg="300
TXT"facebook-domain-verification=jk5lah5nlcwe3uyw7pa81ima5ih750"300
TXT"google-site-verification=OGP_6WTpknrkd5RY6jYjKANnH_b06gyH70HB0hU67kU"300
TXT"pkF/XrCiugn5vQeREoYW7nKQdKGfyrtwVR9DZkEaIbA="300
TXT"v=spf1 include:_u.mz-web.de._spf.smart.ondmarc.com ~all"300
TXT"wbl44t2nv95771q1n30qpfgcsjwwysb5"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 1h, NS 1d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35