bih.de

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

info

nameserver-1-cc.maxcluster.net, nameserver-2-cc.maxcluster.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
nameserver-1-cc.maxcluster.net, nameserver-2-cc.maxcluster.net
NS in the zone
nameserver-1-cc.maxcluster.net, nameserver-2-cc.maxcluster.net
NameserverAddressesNetwork (AS)Glue
nameserver-1-cc.maxcluster.net194.6.209.4 2a00:f48:1008::209:4:10AS47447 TTM - 23M GmbH, DE AS47447 TTM - 23M GmbH, DE-
nameserver-2-cc.maxcluster.net159.69.121.79 2a01:4f8:c010:95a::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: nameserver-1-cc.maxcluster.net, nameserver-2-cc.maxcluster.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: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS47447 (TTM - 23M GmbH, DE): 2 addresses.
  • 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
nameserver-1-cc.maxcluster.net 194.6.209.4NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
nameserver-1-cc.maxcluster.net 2a00:f48:1008::209:4:10NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
nameserver-2-cc.maxcluster.net 159.69.121.79NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
nameserver-2-cc.maxcluster.net 2a01:4f8:c010:95a::1NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: nameserver-1-cc.maxcluster.net: "PowerDNS Authoritative Server 4.1.1"; nameserver-2-cc.maxcluster.net: "PowerDNS Authoritative Server 4.1.1". Hide or replace the version string.
    #17
  • ✓ 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 2026091801 · primary nameserver-1-cc.maxcluster.net

Found

Primary (MNAME)
nameserver-1-cc.maxcluster.net
Contact (RNAME)
info.maxcluster.net
Serial
2026091801
Refresh / retry
3600 s / 1000 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
nameserver-1-cc.maxcluster.net (194.6.209.4)2026091801
nameserver-1-cc.maxcluster.net (2a00:f48:1008::209:4:10)2026091801
nameserver-2-cc.maxcluster.net (159.69.121.79)2026091801
nameserver-2-cc.maxcluster.net (2a01:4f8:c010:95a::1)2026091801

Checks

  • ✓ Serial 2026091801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 16m40s, expire 14d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver nameserver-1-cc.maxcluster.net is one of the listed nameservers.
  • ✓ Contact info@maxcluster.net #25
    The SOA RNAME info.maxcluster.net means info@maxcluster.net.
  • ✓ Date-based serial #26
    The serial 2026091801 follows the YYYYMMDDnn convention (2026-09-18).

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

12 records at the apex

Found

Read from
194.6.209.4:53
TypeValueTTL
SOAnameserver-1-cc.maxcluster.net. info.maxcluster.net. 2026091801 3600 1000 1209600 60086400
NSnameserver-2-cc.maxcluster.net.86400
NSnameserver-1-cc.maxcluster.net.86400
A194.6.211.653600
AAAA2a00:f48:1008::211:65:1021600
MX10 mail-cc.maxcluster.net.21600
TXT"google-site-verification=cbPpavn16U0ZzkHMIwZBbrA1xZbMcLlwvDm_b4e4kLI"21600
TXT"maxcluster-domain-verification=ynfyvhnxcgnxwiy5ot74jaovghjbgsbg"21600
TXT"google-site-verification=R6_IO9VWKUTpy07U4wxAR8no75elUwRl3kDLvVbgWoU"300
TXT"v=spf1 include:spf.sendinblue.com a mx ip4:194.6.209.2 ip6:2a00:f48:1008::209:2:10 ~all"21600
TXT"Sendinblue-code:3ae7dd04c20ce8257756e8a8353a8718"21600
TXT"atlassian-domain-verification=DLaJQAI1a8pCdJ6BpgQT7lan/LdnQ81zCOIF3NRCYZ23QJ7qdpFU4jaCRUR1uyrp"86400

Checks

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