haufe.de

Checked 21 October 2026, 22:42 UTC · via 8.8.8.8
!Passed with warnings
26 passed 1 warning 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

info

ns1.haufegroup.de, ns2.haufegroup.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.haufegroup.de, ns2.haufegroup.com
NS in the zone
ns1.haufegroup.de, ns2.haufegroup.com
NameserverAddressesNetwork (AS)Glue
ns1.haufegroup.de192.174.68.103 2001:67c:1bc::103AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT192.174.68.103 2001:67c:1bc::103
ns2.haufegroup.com176.97.158.103 2001:67c:10b8::103AS1921 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.haufegroup.de, ns2.haufegroup.com.
    #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
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .de.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.haufegroup.de 192.174.68.103NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.haufegroup.de 2001:67c:1bc::103NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.haufegroup.com 176.97.158.103NOERROR, 11 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.haufegroup.com 2001:67c:10b8::103NOERROR, 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.haufegroup.de: "RcodeZero DNS"; ns2.haufegroup.com: "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 1791553160 · primary ns1.haufegroup.de

Found

Primary (MNAME)
ns1.haufegroup.de
Contact (RNAME)
dnsmanager.haufe-lexware.com
Serial
1791553160
Refresh / retry
14400 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.haufegroup.de (192.174.68.103)1791553160
ns1.haufegroup.de (2001:67c:1bc::103)1791553160
ns2.haufegroup.com (176.97.158.103)1791553160
ns2.haufegroup.com (2001:67c:10b8::103)1791553160

Checks

  • ✓ Serial 1791553160 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.haufegroup.de is one of the listed nameservers.
  • ✓ Contact dnsmanager@haufe-lexware.com #25
    The SOA RNAME dnsmanager.haufe-lexware.com means dnsmanager@haufe-lexware.com.
  • ✓ Timestamp serial #26
    The serial 1791553160 is a Unix timestamp (2026-10-09 13:39 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
56333ECDSAP256SHA256 (13)SHA256 AAB2865DB848C9FA…yes

DNSKEY in the zone

Key tagRoleAlgorithm
29825ZSK (256)ECDSAP256SHA256 (13)
56333KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 56333 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

26 records at the apex

Found

Read from
192.174.68.103:53
TypeValueTTL
SOAns1.haufegroup.de. dnsmanager.haufe-lexware.com. 1791553160 14400 1800 1209600 360086400
NSns1.haufegroup.de.3600
NSns2.haufegroup.com.3600
A18.185.43.1160
A63.181.17.21160
A63.181.45.960
MX10 mail.haufe.de.3600
MX20 mail2.haufe.de.3600
MX30 mail3.haufe.de.3600
TXT"MS=ms39507417"3600
TXT"MS=ms44163394"3600
TXT"MS=ms97268259"3600
TXT"00D0Q0000008dSF=1TB9Z0000000Mer"3600
TXT"00D24000000GyjS=1TBQF0000000Gxd"3600
TXT"00D9V00000Q1EA2=1TB9V0000000WCn"3600
TXT"_7mipv7pdul328juvn5kghd7wp9lruay"3600
TXT"_gxwn9zy7bi7ond2xilvc3v0svqektj6"3600
TXT"_rzlbwtvbgujhycf2q99hj9ars90vnux"3600
TXT"t4plp3qqby7frdvsbhwbdggy6xy60svt"3600
TXT"swisssign-check=zuX5tl-ZqJxavGGY2nQZuUf4eGM"3600
TXT"2020100620212333o94q3l2197yg8tdplyysp9otb11wlbft5eci1aw6ziszi35q"3600
TXT"202010150055291gjvab6gnx2orxwm5peqaa3cp3caw6rzeru9jptmfdkj0g6szx"3600
TXT"google-site-verification=Aa2R1El1t-k-C6qr_cWQNe-5iBmiMC5hY27HnSFwEWA"3600
TXT"google-site-verification=iAfZ6S74YtjPuII36z63xiTaG2XkUpyzvnzhvlVJ72s"3600
TXT"bkDLsJ8NWESMhXDjENY0mkmt3BIkeDJ0sQ7FGhFiWreHNzXxGpMdiHWUO99qzqANRXD7Q6o4cTx3K3gJsdg7zA=="3600
TXT"v=spf1 +mx include:adns.haufe.de ip4:185.150.244.238 ip4:20.52.209.98 ip4:217.31.84.77 ip4:217.31.86.164 ip4:217.31.84.34 ip4:84.17.184.240/28 ip4:18.196.4.250 ~all"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ 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