barmenia.de

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

warn

ns.barmenia.de, nsb.barmenia.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.barmenia.de, nsb.barmenia.de
NS in the zone
ns.barmenia.de, nsb.barmenia.de
NameserverAddressesNetwork (AS)Glue
ns.barmenia.de195.128.40.42AS20546 SOPRADO-ANY - SOPRADO GmbH, DE195.128.40.42
nsb.barmenia.de195.128.41.42AS29105 BARMENIA-AS - Barmenia Krankenversicherung a.G., DE195.128.41.42

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.barmenia.de, nsb.barmenia.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns.barmenia.de, nsb.barmenia.de.
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20546 (SOPRADO-ANY - SOPRADO GmbH, DE): 1 address; AS29105 (BARMENIA-AS - Barmenia Krankenversicherung a.G., DE): 1 address.
  • 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
  • !
    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
ns.barmenia.de 195.128.40.42NOERROR, 15 ms, authoritativenoyes / yesrefusedFreibier
nsb.barmenia.de 195.128.41.42NOERROR, 13 ms, authoritativenoyes / yesrefused9.18.29

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: nsb.barmenia.de: "9.18.29". 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 2026102000 · primary ns.barmenia.de

Found

Primary (MNAME)
ns.barmenia.de
Contact (RNAME)
pc-service.barmenia.de
Serial
2026102000
Refresh / retry
1800 s / 300 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns.barmenia.de (195.128.40.42)2026102000
nsb.barmenia.de (195.128.41.42)2026102000

Checks

  • ✓ Serial 2026102000 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 30m, retry 5m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.barmenia.de is one of the listed nameservers.
  • ✓ Contact pc-service@barmenia.de #25
    The SOA RNAME pc-service.barmenia.de means pc-service@barmenia.de.
  • ✓ Date-based serial #26
    The serial 2026102000 follows the YYYYMMDDnn convention (2026-10-20).

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

19 records at the apex

Found

Read from
195.128.40.42:53
TypeValueTTL
SOAns.barmenia.de. pc-service.barmenia.de. 2026102000 1800 300 1209600 300300
NSns.barmenia.de.300
NSnsb.barmenia.de.300
A195.128.40.32300
MX10 barmenia-de.mail.protection.outlook.com.300
TXT"globalsign-domain-verification=5D718878A5DE10453C6DCA8243CB53CF"300
TXT"v=spf1 a:mx.barmenia.com include:mcxplatform.de include:spf.hypeinnovation.com a:mx.adcuri-partner.de a:mail-gw.itw.de" " include:spf.mandrillapp.com include:spf.protection.outlook.com include:spf-de.emailsignatures365.com -all"300
TXT"atlassian-domain-verification=0KTiana6Y5nelQdkkTaCCavlKPXzOb9im/aXCY1XMWt2cTMUpH2mBNs1XBeymEVL"300
TXT"jamf-site-verification=qbXj-LamkUkfH7nqQ3guzg"300
TXT"MS=ms94958067"300
TXT"teamviewer-sso-verification=a7257ee4b4e348f3b12dd6e1f544abef"300
TXT"apple-domain-verification=241Nidhv76VcRmIZ"300
TXT"google-site-verification=0lZ3AnOxBH0iDj7lb1IMByCF2VtXF5DdppzThe_JE6g"300
TXT"miro-verification=d0d2db7ad779686203a3fdd78e5bee19ac6652f2"300
TXT"figma-domain-verification=c667d64bc232776bf399a2cc936c4d3f782e6156b256e99fb9079ca5acb123f6-1772532034"300
TXT"mentimeter-211140e6-61a2-4e35-ae50-1c38d48ce265"300
TXT"OyjFhr4GD/rjmkjtOPWhDdRKURHVZPsgoJLwG+J6PFA="300
TXT"intersight=7f889e06b481e34fff339fbae77ac82de1ccbbfdccd407461514520a1860bb9e"300
TXT"facebook-domain-verification=iscwv3i92m48vs5q61d55adm0owc7i"300

Checks

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