bremerhaven.de

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

warn

ns-02.briteline.de, ns01.bremerhaven.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns-02.briteline.de, ns01.bremerhaven.de
NS in the zone
ns-02.briteline.de, ns01.bremerhaven.de
NameserverAddressesNetwork (AS)Glue
ns-02.briteline.de82.198.211.1 2a03:9981:0:191::2222AS30742 BRITELINE-AS - Bremen Briteline GmbH, DE AS30742 BRITELINE-AS - Bremen Briteline GmbH, DE82.198.211.1
ns01.bremerhaven.de185.204.97.31 2a0a:f540:feed:150::13AS210759 asn-bit - Stadt Bremerhaven trading as Betrieb fuer Informationstechnologie Bremerhaven, DE AS210759 asn-bit - Stadt Bremerhaven trading as Betrieb fuer Informationstechnologie Bremerhaven, DE185.204.97.31

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns-02.briteline.de, ns01.bremerhaven.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns-02.briteline.de (glue 82.198.211.1, zone 82.198.211.1, 2a03:9981:0:191::2222); ns01.bremerhaven.de (glue 185.204.97.31, zone 185.204.97.31, 2a0a:f540:feed:150::13). Update the glue at your registrar.
    #8
  • ✓ 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: AS210759 (asn-bit - Stadt Bremerhaven trading as Betrieb fuer Informationstechnologie Bremerhaven, DE): 2 addresses; AS30742 (BRITELINE-AS - Bremen Briteline GmbH, DE): 2 addresses.
  • i
    All nameserver names under .de
    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
ns-02.briteline.de 82.198.211.1NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns-02.briteline.de 2a03:9981:0:191::2222NOERROR, 39 ms, authoritativenoyes / yesrefused-
ns01.bremerhaven.de 185.204.97.31NOERROR, 19 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian
ns01.bremerhaven.de 2a0a:f540:feed:150::13NOERROR, 11 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian

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: ns01.bremerhaven.de: "9.20.29-1~deb13u1-Debian". 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 2114091023 · primary ns01.bremerhaven.de

Found

Primary (MNAME)
ns01.bremerhaven.de
Contact (RNAME)
hostmaster.bit.bremerhaven.de
Serial
2114091023
Refresh / retry
43200 s / 7200 s
Expire
2419200 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns-02.briteline.de (82.198.211.1)2114091023
ns-02.briteline.de (2a03:9981:0:191::2222)2114091023
ns01.bremerhaven.de (185.204.97.31)2114091023
ns01.bremerhaven.de (2a0a:f540:feed:150::13)2114091023

Checks

  • ✓ Serial 2114091023 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 28d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.bremerhaven.de is one of the listed nameservers.
  • ✓ Contact hostmaster@bit.bremerhaven.de #25
    The SOA RNAME hostmaster.bit.bremerhaven.de means hostmaster@bit.bremerhaven.de.
  • ✓ Timestamp serial #26
    The serial 2114091023 is a Unix timestamp (2036-12-28 15:30 UTC).

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

9 records at the apex

Found

Read from
82.198.211.1:53
TypeValueTTL
SOAns01.bremerhaven.de. hostmaster.bit.bremerhaven.de. 2114091023 43200 7200 2419200 8640086400
NSns-02.briteline.de.86400
NSns01.bremerhaven.de.86400
A185.204.97.9886400
AAAA2a0a:f540:feed:2::1986400
MX20 mail.bremerhaven.de.86400
TXT"google-site-verification=U9UyieoBvtoUR_Ea_tVad0fHYGwglaG8Dn-H7f1UqDw"300
TXT"v=spf1 ip4:185.204.97.95 a:otc-de-spf.mms.t-systems-service.com a:kundentest.form-solutions.de -all"300
TXT"qs0sidavgtuq9s7f0aj7dnnq36"300

Checks

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