bnotk.de

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

pass

ns.hrb.de, ns1.rox.net, ns2.rox.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.hrb.de, ns1.rox.net, ns2.rox.net
NS in the zone
ns.hrb.de, ns1.rox.net, ns2.rox.net
NameserverAddressesNetwork (AS)Glue
ns.hrb.de185.194.236.7 2a0a:51c0::2fbAS48314 IP-PROJECTS - Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG, DE AS48314 IP-PROJECTS - Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG, DE185.194.236.7 2a0a:51c0::2fb
ns1.rox.net192.174.68.119 2001:67c:1bc::119AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.rox.net176.97.158.119 2001:67c:10b8::119AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.hrb.de, ns1.rox.net, ns2.rox.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 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses; AS48314 (IP-PROJECTS - Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.hrb.de 185.194.236.7NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.4 (built Feb 6 2025 15:18:23 by root@localhost)
ns.hrb.de 2a0a:51c0::2fbNOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.4 (built Feb 6 2025 15:18:23 by root@localhost)
ns1.rox.net 192.174.68.119NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.rox.net 2001:67c:1bc::119NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.rox.net 176.97.158.119NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.rox.net 2001:67c:10b8::119NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1

Checks

  • ✓ All respond #14
    All 6 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: ns.hrb.de: "PowerDNS Authoritative Server 4.9.4 (built Feb 6 2025 15:18:23 by root@localhost)". 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 2026101302 · primary ns1.rox.net

Found

Primary (MNAME)
ns1.rox.net
Contact (RNAME)
dns.rockenstein.de
Serial
2026101302
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.hrb.de (185.194.236.7)2026101302
ns.hrb.de (2a0a:51c0::2fb)2026101302
ns1.rox.net (192.174.68.119)2026101302
ns1.rox.net (2001:67c:1bc::119)2026101302
ns2.rox.net (176.97.158.119)2026101302
ns2.rox.net (2001:67c:10b8::119)2026101302

Checks

  • ✓ Serial 2026101302 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.rox.net is one of the listed nameservers.
  • ✓ Contact dns@rockenstein.de #25
    The SOA RNAME dns.rockenstein.de means dns@rockenstein.de.
  • ✓ Date-based serial #26
    The serial 2026101302 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

13 records at the apex

Found

Read from
185.194.236.7:53
TypeValueTTL
SOAns1.rox.net. dns.rockenstein.de. 2026101302 10800 3600 604800 36003600
NSns2.rox.net.3600
NSns.hrb.de.3600
NSns1.rox.net.3600
A77.76.215.1853600
MX5 mail3.rox.net.300
MX20 mail2.rox.net.300
MX10 mail1.rox.net.300
TXT"amazon-business-verification=512779a9fc70a648283e4c424b904c6601219f745d7263b619f14f77e80e8fcd"3600
TXT"atlassian-domain-verification=SN6moqxNyKXFZ3TyhHl3KyvdPu2n1PH0AfR5zs3aYMcZovTpu5JhITXXBCTzKcJF"3600
TXT"v=spf1 mx ip4:77.76.215.128/25 a:smtp.notarnet.de a:smtp.hrb.de include:spf.rockenstein.de -all"3600
TXT"MS=6E0006EA81059CD0D15FF8E40F56066C4A421009"3600
TXT"MS=ms34806785"3600

Checks

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