model-kartei.de

Checked 21 October 2026, 23:30 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 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

ns.routing.net, ns8.routing.net, ns9.routing.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.routing.net, ns8.routing.net, ns9.routing.net
NS in the zone
ns.routing.net, ns8.routing.net, ns9.routing.net
NameserverAddressesNetwork (AS)Glue
ns.routing.net134.0.30.178AS48823 AS48823 - Hosting.de GmbH, DE-
ns8.routing.net194.50.113.2AS41637 ROUTING-ANYCAST - Hosting.de GmbH, DE-
ns9.routing.net194.126.196.2AS31400 ACCELERATED-IT - firstcolo GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.routing.net, ns8.routing.net, ns9.routing.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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS31400 (ACCELERATED-IT - firstcolo GmbH, DE): 1 address; AS41637 (ROUTING-ANYCAST - Hosting.de GmbH, DE): 1 address; AS48823 (AS48823 - Hosting.de GmbH, DE): 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.routing.net 134.0.30.178NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns8.routing.net 194.50.113.2NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns9.routing.net 194.126.196.2NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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 2026101300 · primary ns.routing.net

Found

Primary (MNAME)
ns.routing.net
Contact (RNAME)
steiner.lantopic.de
Serial
2026101300
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns.routing.net (134.0.30.178)2026101300
ns8.routing.net (194.50.113.2)2026101300
ns9.routing.net (194.126.196.2)2026101300

Checks

  • ✓ Serial 2026101300 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.routing.net is one of the listed nameservers.
  • ✓ Contact steiner@lantopic.de #25
    The SOA RNAME steiner.lantopic.de means steiner@lantopic.de.
  • ✓ Date-based serial #26
    The serial 2026101300 follows the YYYYMMDDnn convention (2026-10-13).

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

10 records at the apex

Found

Read from
134.0.30.178:53
TypeValueTTL
SOAns.routing.net. steiner.lantopic.de. 2026101300 14400 3600 604800 9007200
NSns8.routing.net.7200
NSns.routing.net.7200
NSns9.routing.net.7200
A80.86.187.303600
A80.86.187.283600
A80.86.187.213600
MX10 mx.model-kartei.de.3600
TXT"google-site-verification=UKPXcF3BgyBeuCK74fnRdPjIZwbQ9uMh1kzSDhB4bK8"7200
TXT"v=spf1 ip4:80.86.187.0/25 -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 2h. The NS TTL at the parent is 1d and in the zone 2h; 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
  • 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