z0r.de

Checked 22 October 2026, 01:10 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 5 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

a.xnameserver.de, b.xnameserver.de, c.xnameserver.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
a.xnameserver.de, b.xnameserver.de, c.xnameserver.de
NS in the zone
a.xnameserver.de, b.xnameserver.de, c.xnameserver.de
NameserverAddressesNetwork (AS)Glue
a.xnameserver.de192.174.68.104 2001:67c:1bc::104AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT192.174.68.104 2001:67c:1bc::104
b.xnameserver.de176.97.158.104 2001:67c:10b8::104AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT176.97.158.104 2001:67c:10b8::104
c.xnameserver.de45.87.158.53 2a02:d500::53AS48596 INWX - InterNetworX Management GmbH, DE AS48596 INWX - InterNetworX Management GmbH, DE45.87.158.53 2a02:d500::53

Checks

  • ✓ 3 nameservers #6
    Delegated to a.xnameserver.de, b.xnameserver.de, c.xnameserver.de.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses; AS48596 (INWX - InterNetworX Management GmbH, DE): 2 addresses.
  • i
    All nameserver names under .de
    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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a.xnameserver.de 192.174.68.104NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
a.xnameserver.de 2001:67c:1bc::104NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
b.xnameserver.de 176.97.158.104NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
b.xnameserver.de 2001:67c:10b8::104NOERROR, 14 ms, authoritativenoyes / yesrefusedreg-wie1
c.xnameserver.de 45.87.158.53NOERROR, 12 ms, authoritativenoyes / yesrefusedINWX AXFR Server
c.xnameserver.de 2a02:d500::53NOERROR, 12 ms, authoritativenoyes / yesrefusedINWX AXFR Server

Checks

  • ✓ All respond #14
    All 6 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: a.xnameserver.de: "RcodeZero DNS"; b.xnameserver.de: "reg-wie1"; c.xnameserver.de: "INWX AXFR Server".
    #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 2026021102 · primary a.xnameserver.de

Found

Primary (MNAME)
a.xnameserver.de
Contact (RNAME)
hostmaster.inwx.de
Serial
2026021102
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
a.xnameserver.de (192.174.68.104)2026021102
a.xnameserver.de (2001:67c:1bc::104)2026021102
b.xnameserver.de (176.97.158.104)2026021102
b.xnameserver.de (2001:67c:10b8::104)2026021102
c.xnameserver.de (45.87.158.53)2026021102
c.xnameserver.de (2a02:d500::53)2026021102

Checks

  • ✓ Serial 2026021102 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a.xnameserver.de is one of the listed nameservers.
  • ✓ Contact hostmaster@inwx.de #25
    The SOA RNAME hostmaster.inwx.de means hostmaster@inwx.de.
  • ✓ Date-based serial #26
    The serial 2026021102 follows the YYYYMMDDnn convention (2026-02-11).

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

14 records at the apex

Found

Read from
192.174.68.104:53
TypeValueTTL
SOAa.xnameserver.de. hostmaster.inwx.de. 2026021102 10800 3600 604800 360086400
NSa.xnameserver.de.3600
NSb.xnameserver.de.3600
NSc.xnameserver.de.3600
A91.98.167.204300
MX1 aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX10 aspmx2.googlemail.com.3600
MX10 aspmx3.googlemail.com.3600
MX10 aspmx4.googlemail.com.3600
MX10 aspmx5.googlemail.com.3600
CAA0 issue "letsencrypt.org"3600
CAA0 issue "zerossl.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
  • ✓ 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, zerossl.com.