oberstdorf.de

Checked 21 October 2026, 23:41 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

info

ns1.dns.speedkom.net, ns2.dns.speedkom.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.dns.speedkom.net, ns2.dns.speedkom.net
NS in the zone
ns1.dns.speedkom.net, ns2.dns.speedkom.net
NameserverAddressesNetwork (AS)Glue
ns1.dns.speedkom.net213.182.0.1 2001:14e0::1AS12931 IDKOM - IDKOM Networks GmbH, DE AS12931 IDKOM - IDKOM Networks GmbH, DE-
ns2.dns.speedkom.net213.182.13.8 2a03:f80:31:9ada::1AS12931 IDKOM - IDKOM Networks GmbH, DE AS57169 EDIS-AS-EU - EDIS GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dns.speedkom.net, ns2.dns.speedkom.net.
    #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 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12931 (IDKOM - IDKOM Networks GmbH, DE): 3 addresses; AS57169 (EDIS-AS-EU - EDIS GmbH, AT): 1 address.
  • i
    All nameserver names under .net
    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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dns.speedkom.net 213.182.0.1NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns1.dns.speedkom.net 2001:14e0::1NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns2.dns.speedkom.net 213.182.13.8NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2.dns.speedkom.net 2a03:f80:31:9ada::1NOERROR, 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

warn

serial 2018089615 · primary ns1.dns.speedkom.net

Found

Primary (MNAME)
ns1.dns.speedkom.net
Contact (RNAME)
hostmaster.speedkom.net
Serial
2018089615
Refresh / retry
21600 s / 1800 s
Expire
604800 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns1.dns.speedkom.net (213.182.0.1)2018089615
ns1.dns.speedkom.net (2001:14e0::1)2018089615
ns2.dns.speedkom.net (213.182.13.8)2018089615
ns2.dns.speedkom.net (2a03:f80:31:9ada::1)2018089615

Checks

  • ✓ Serial 2018089615 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 6h, retry 30m, expire 7d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dns.speedkom.net is one of the listed nameservers.
  • ✓ Contact hostmaster@speedkom.net #25
    The SOA RNAME hostmaster.speedkom.net means hostmaster@speedkom.net.
  • ✓ Timestamp serial #26
    The serial 2018089615 is a Unix timestamp (2033-12-13 12:26 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
1 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
33186ECDSAP256SHA256 (13)SHA256 66616C4DF0498C05…yes

DNSKEY in the zone

Key tagRoleAlgorithm
33186KSK (257)ECDSAP256SHA256 (13)
60490ZSK (256)ECDSAP256SHA256 (13)

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 33186 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-01 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-01 09:23 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

8 records at the apex

Found

Read from
213.182.0.1:53
TypeValueTTL
SOAns1.dns.speedkom.net. hostmaster.speedkom.net. 2018089615 21600 1800 604800 17280086400
NSns2.dns.speedkom.net.86400
NSns1.dns.speedkom.net.86400
A213.182.18.1386400
MX200 mailin2.mx.speedkom.net.86400
MX300 mailin5.mx.speedkom.net.86400
TXT"v=spf1 include:amazonses.com include:spf1.spf.speedkom.net ~all"3600
TXT"MS=ms39869086"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, 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