stadtgeschichtliches-museum-leipzig.de

Checked 22 October 2026, 00:30 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 6 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.ordergate.biz, ns2.ordergate.biz

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.ordergate.biz, ns2.ordergate.biz
NS in the zone
ns.ordergate.biz, ns2.ordergate.biz
NameserverAddressesNetwork (AS)Glue
ns.ordergate.biz213.9.14.107AS12676 NCORE-AS - HKN GmbH, DE-
ns2.ordergate.biz217.79.214.245AS15830 Equinix - Equinix (EMEA) Acquisition Enterprises B.V., NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.ordergate.biz, ns2.ordergate.biz.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12676 (NCORE-AS - HKN GmbH, DE): 1 address; AS15830 (Equinix - Equinix (EMEA) Acquisition Enterprises B.V., NL): 1 address.
  • i
    All nameserver names under .biz
    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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.ordergate.biz 213.9.14.107NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns2.ordergate.biz 217.79.214.245NOERROR, 7 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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 2017100501 · primary ns.ordergate.biz

Found

Primary (MNAME)
ns.ordergate.biz
Contact (RNAME)
hostmaster.ordergate.biz
Serial
2017100501
Refresh / retry
86400 s / 28800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.ordergate.biz (213.9.14.107)2017100501
ns2.ordergate.biz (217.79.214.245)2017100501

Checks

  • ✓ Serial 2017100501 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 8h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.ordergate.biz is one of the listed nameservers.
  • ✓ Contact hostmaster@ordergate.biz #25
    The SOA RNAME hostmaster.ordergate.biz means hostmaster@ordergate.biz.
  • ✓ Date-based serial #26
    The serial 2017100501 follows the YYYYMMDDnn convention (2017-10-05).

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
213.9.14.107:53
TypeValueTTL
SOAns.ordergate.biz. hostmaster.ordergate.biz. 2017100501 86400 28800 604800 36003600
NSns.ordergate.biz.3600
NSns2.ordergate.biz.3600
A213.187.93.503600
MX10 mail.stadtgeschichtliches-museum-leipzig.de.3600

Checks

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