kdo.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
27 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

warn

ans0.ewetel.de, ans1.ewetel.net, ans2.ewetel.de, ans3.ewetel.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ans0.ewetel.de, ans1.ewetel.net, ans2.ewetel.de, ans3.ewetel.net
NS in the zone
ans0.ewetel.de, ans1.ewetel.net, ans2.ewetel.de, ans3.ewetel.net
NameserverAddressesNetwork (AS)Glue
ans0.ewetel.de80.228.127.14AS9145 EWETEL - EWE TEL GmbH, DE80.228.127.14
ans1.ewetel.net213.170.187.14AS9145 EWETEL - EWE TEL GmbH, DE-
ans2.ewetel.de212.6.121.254AS9145 EWETEL - EWE TEL GmbH, DE212.6.121.254
ans3.ewetel.net85.16.255.14AS9145 EWETEL - EWE TEL GmbH, DE-

Checks

  • ✓ 4 nameservers #6
    Delegated to ans0.ewetel.de, ans1.ewetel.net, ans2.ewetel.de, ans3.ewetel.net.
  • ✓ 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 4 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS9145 (EWETEL - EWE TEL GmbH, DE): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ans0.ewetel.de 80.228.127.14NOERROR, 11 ms, authoritativenoyes / yesrefused-
ans1.ewetel.net 213.170.187.14NOERROR, 11 ms, authoritativenoyes / yesrefused-
ans2.ewetel.de 212.6.121.254NOERROR, 11 ms, authoritativenoyes / yesrefused-
ans3.ewetel.net 85.16.255.14NOERROR, 11 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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.
  • ✓ 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.
  • ✓ 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 2026093278 · primary ans0.ewetel.de

Found

Primary (MNAME)
ans0.ewetel.de
Contact (RNAME)
hostmaster.ewetel.net
Serial
2026093278
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ans0.ewetel.de (80.228.127.14)2026093278
ans1.ewetel.net (213.170.187.14)2026093278
ans2.ewetel.de (212.6.121.254)2026093278
ans3.ewetel.net (85.16.255.14)2026093278

Checks

  • ✓ Serial 2026093278 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ans0.ewetel.de is one of the listed nameservers.
  • ✓ Contact hostmaster@ewetel.net #25
    The SOA RNAME hostmaster.ewetel.net means hostmaster@ewetel.net.
  • ✓ Timestamp serial #26
    The serial 2026093278 is a Unix timestamp (2034-03-16 03:41 UTC).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
31 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
25113RSASHA256 (8)SHA256 A4993DC38DE56BCF…yes
24280RSASHA256 (8)SHA256 C91EC2129E1367B8…yes

DNSKEY in the zone

Key tagRoleAlgorithm
25113ZSK (256)RSASHA256 (8)
24280KSK (257)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 25113 (SHA256), key tag 24280 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-10-31 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-31 15:17 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

12 records at the apex

Found

Read from
80.228.127.14:53
TypeValueTTL
SOAans0.ewetel.de. hostmaster.ewetel.net. 2026093278 10800 3600 604800 60086400
NSans1.ewetel.net.86400
NSans0.ewetel.de.86400
NSans3.ewetel.net.86400
NSans2.ewetel.de.86400
A194.76.66.12900
MX10 mta2in.kdo.de.900
MX10 mta1in.kdo.de.900
TXT"v=spf1 mx ip4:194.76.65.37/32 ip4:194.76.65.40/32 ip4:194.76.65.116/32 ip4:194.76.65.109/32 ip4:194.76.65.119/32 -all"900
TXT"swisssign-check=2uXHJmzPEpJpAuPnUo2YbPLG4a4"900
TXT"anny-verification=a36eddd3-677a-4443-a2b4-6c551e0d2d84"900
TXT"atlassian-domain-verification=5fWrztvU77tYu63xYppHqmrT0yO0t2VjBD57aTmMych/i9i8XdZ0aqAvyIAiqCJR"900

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, MX 15m, NS 1d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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