xlx-owl.de

Checked 22 October 2026, 01:10 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 2 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

warn

ns1.coreroute.de, ns2.coreroute.de, ns3.coreroute.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.coreroute.de, ns2.coreroute.de, ns3.coreroute.de
NS in the zone
ns1.coreroute.de, ns2.coreroute.de, ns3.coreroute.de
NameserverAddressesNetwork (AS)Glue
ns1.coreroute.de104.156.136.44AS49585 COREROUTE-AS - CoreRoute UG, DE-
ns2.coreroute.de23.146.24.55AS49585 COREROUTE-AS - CoreRoute UG, DE-
ns3.coreroute.de208.167.237.33AS20473 AS-VULTR - The Constant Company, LLC, US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.coreroute.de, ns2.coreroute.de, ns3.coreroute.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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20473 (AS-VULTR - The Constant Company, LLC, US): 1 address; AS49585 (COREROUTE-AS - CoreRoute UG, 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.coreroute.de 104.156.136.44NOERROR, 17 ms, authoritativenoyes / norefused-
ns2.coreroute.de 23.146.24.55NOERROR, 17 ms, authoritativenoyes / norefused-
ns3.coreroute.de 208.167.237.33SERVFAIL, 255 ms, NOT authoritativenono / norefused-

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns3.coreroute.de (208.167.237.33): SERVFAIL, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns3.coreroute.de (208.167.237.33): .
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.coreroute.de (104.156.136.44), ns2.coreroute.de (23.146.24.55), ns3.coreroute.de (208.167.237.33).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2025120301 · primary ns1.coreroute.de

Found

Primary (MNAME)
ns1.coreroute.de
Contact (RNAME)
hostmaster.coreroute.de
Serial
2025120301
Refresh / retry
3600 s / 900 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.coreroute.de (104.156.136.44)2025120301
ns2.coreroute.de (23.146.24.55)2025120301

Checks

  • ✓ Serial 2025120301 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.coreroute.de is one of the listed nameservers.
  • ✓ Contact hostmaster@coreroute.de #25
    The SOA RNAME hostmaster.coreroute.de means hostmaster@coreroute.de.
  • ✓ Date-based serial #26
    The serial 2025120301 follows the YYYYMMDDnn convention (2025-12-03).

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

5 records at the apex

Found

Read from
104.156.136.44:53
TypeValueTTL
SOAns1.coreroute.de. hostmaster.coreroute.de. 2025120301 3600 900 604800 8640086400
NSns3.coreroute.de.86400
NSns2.coreroute.de.86400
NSns1.coreroute.de.86400
A104.156.136.81800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, 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