bauder.de

Checked 21 October 2026, 21:36 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 0 failed 7 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.hotbytes.net, ns2.hotbytes.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.hotbytes.net, ns2.hotbytes.net
NS in the zone
ns1.hotbytes.net, ns2.hotbytes.net
NameserverAddressesNetwork (AS)Glue
ns1.hotbytes.net193.227.117.225 2a04:2b00:14cc::225AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.hotbytes.net194.50.187.225 2a04:2b00:14dd::225AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.hotbytes.net, ns2.hotbytes.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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.hotbytes.net 193.227.117.225NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.hotbytes.net 2a04:2b00:14cc::225NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.hotbytes.net 194.50.187.225NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.hotbytes.net 2a04:2b00:14dd::225NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.hotbytes.net: "RcodeZero DNS"; ns2.hotbytes.net: "reg-wie1".
    #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 2026101914 · primary ns1.hotbytes.net

Found

Primary (MNAME)
ns1.hotbytes.net
Contact (RNAME)
tech.rrpproxy.net
Serial
2026101914
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
28800 s

Serial per nameserver

NameserverSerial
ns1.hotbytes.net (193.227.117.225)2026101914
ns1.hotbytes.net (2a04:2b00:14cc::225)2026101914
ns2.hotbytes.net (194.50.187.225)2026101914
ns2.hotbytes.net (2a04:2b00:14dd::225)2026101914

Checks

  • ✓ Serial 2026101914 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 8h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.hotbytes.net is one of the listed nameservers.
  • ✓ Contact tech@rrpproxy.net #25
    The SOA RNAME tech.rrpproxy.net means tech@rrpproxy.net.
  • ✓ Date-based serial #26
    The serial 2026101914 follows the YYYYMMDDnn convention (2026-10-19).

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

23 records at the apex

Found

Read from
193.227.117.225:53
TypeValueTTL
SOAns1.hotbytes.net. tech.rrpproxy.net. 2026101914 10800 3600 1209600 2880028800
NSns1.hotbytes.net.28800
NSns2.hotbytes.net.28800
A37.202.2.1031800
MX10 bauder-de-1.fortimailcloud.com.3600
MX20 bauder-de-2.fortimailcloud.com.3600
TXT"MS=ms77491963"28800
TXT"00D1r000001Gq0V=1TBTr00000005xN"28800
TXT"apple-domain-verification=aqKLwwbUbSHQ56Sh"28800
TXT"MS=6D3FC8D15D0D268B83CA596FDF3103CE38D6CB4A"28800
TXT"nitro-verification-code=LTIyMjY5NzAzNzI4NzAxMjI5MjQ="28800
TXT"miro-verification=2f5968c54797c53518ca02b95f12cecc40c51d99"28800
TXT"ms-domain-verification=0fa8fc3e-ebf2-4445-9a46-be85144d52dc"28800
TXT"teamviewer-sso-verification=bd24ff94dbfc4dd3be48124f5e023b17"28800
TXT"anthropic-domain-verification-01jhtp=ZtZbW8WeaNcbEBOwLUgUiFeME"28800
TXT"slack-domain-verification=k8HzlrLWkujUXtDNJD9UgcI5f9W4hgu9djOjJTSn"28800
TXT"google-site-verification=Rv1XCSaF0ZPyu1W_uRdgXxvsEb__n3d08HGUQ_7vWdc"28800
TXT"google-site-verification=Tii9kFpXTEtQaFLPtS2i1YyNlsHi_OVk2ur9jP8N1h0"28800
TXT"_globalsign-domain-verification=DUOmCxQHTV1gfc0_SdafW4TDgNYtFB-0hdZzBIxsCw"28800
TXT"pardot1011671=c445a6831924f6f398035a5d501ccf9f0aa3f589d4da57b35118fc076a912196"28800
TXT"sending_domain1011671=e93140e3fcb981974015b4d79da5c32627010e9d1a617acd6527f771f9857605"28800
TXT"b3o/LcTpBos1KcgAAppS6KPJS3RpsMWurq4y8kCtP0Efxl8UTNXvpS4InZX6jIampYBL60NheW7P0yWUU8Dy7A=="28800
TXT"v=spf1 mx a:mailout.bauder.cloud ip4:217.111.18.237 ip4:217.111.18.228 ip4:217.111.18.229 ip4:62.96.8.233 ip4:185.228.9.1 " "include:spf.protection.outlook.com include:agenturserver.de include:_spf.salesforce.com include:_spf.fortimailcloud.com include:spf.crsend.com include:aspmx.pardot.com -all"28800

Checks

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