block-house.de

Checked 21 October 2026, 21:48 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 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

warn

ns1.ennit.net, ns2.ennit.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ennit.net, ns2.ennit.net
NS in the zone
ns1.ennit.net, ns2.ennit.net
NameserverAddressesNetwork (AS)Glue
ns1.ennit.net213.178.66.161AS13101 TNG-AS - TNG Stadtnetz GmbH, DE-
ns2.ennit.net82.97.146.5AS13101 TNG-AS - TNG Stadtnetz GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ennit.net, ns2.ennit.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13101 (TNG-AS - TNG Stadtnetz GmbH, DE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ennit.net 213.178.66.161NOERROR, 14 ms, authoritativenoyes / yesrefused9.7.0-P1
ns2.ennit.net 82.97.146.5NOERROR, 11 ms, authoritativenoyes / yesrefused9.10.3-P4-Ubuntu

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ennit.net: "9.7.0-P1"; ns2.ennit.net: "9.10.3-P4-Ubuntu". 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 2026100901 · primary ns1.ennit.net

Found

Primary (MNAME)
ns1.ennit.net
Contact (RNAME)
hostmaster.support.ennit.de
Serial
2026100901
Refresh / retry
14400 s / 7200 s
Expire
3600000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.ennit.net (213.178.66.161)2026100901
ns2.ennit.net (82.97.146.5)2026100901

Checks

  • ✓ Serial 2026100901 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 1000h, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ennit.net is one of the listed nameservers.
  • ✓ Contact hostmaster@support.ennit.de #25
    The SOA RNAME hostmaster.support.ennit.de means hostmaster@support.ennit.de.
  • ✓ Date-based serial #26
    The serial 2026100901 follows the YYYYMMDDnn convention (2026-10-09).

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

11 records at the apex

Found

Read from
213.178.66.161:53
TypeValueTTL
SOAns1.ennit.net. hostmaster.support.ennit.de. 2026100901 14400 7200 3600000 864007200
NSns2.ennit.net.7200
NSns1.ennit.net.7200
A91.107.208.1607200
MX10 blockhouse-de01c.mail.protection.outlook.com.7200
TXT"brevo-code:adfe317361be696a6b4b2dd776d7c817"7200
TXT"openai-domain-verification=dv-DXABoQZ4NFmU60gQcVysA0Jv"7200
TXT"anthropic-domain-verification-961hw5=axgVHZEEPWB6TTFoLBdfWIgIp"7200
TXT"v=spf1 include:_spf.block-systems.de a:mail02.fse.intershop.de include:spf.agnitas.de include:spf.haj.tech -all"7200
TXT"MS=ms82261408"7200
TXT"apple-domain-verification=oXfXueMu22R0ws09"7200

Checks

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