bg-verkehr.de

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

info

hns1.mcs.de, hns2.mcs.de, ns.siguv.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
hns1.mcs.de, hns2.mcs.de, ns.siguv.de
NS in the zone
hns1.mcs.de, hns2.mcs.de, ns.siguv.de
NameserverAddressesNetwork (AS)Glue
hns1.mcs.de147.78.89.172 2a09:2040:0:10::10AS215992 MCS-AS - MCS GmbH, DE AS215992 MCS-AS - MCS GmbH, DE-
hns2.mcs.de162.19.245.172 2001:41d0:701:1100::4284AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns.siguv.de193.104.3.200AS51053 BGF-AS - Berufsgenossenschaft Verkehrswirtschaft Post-Logistik Telekommunikation (BG Verkehr), DE193.104.3.200

Checks

  • ✓ 3 nameservers #6
    Delegated to hns1.mcs.de, hns2.mcs.de, ns.siguv.de.
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS215992 (MCS-AS - MCS GmbH, DE): 2 addresses; AS51053 (BGF-AS - Berufsgenossenschaft Verkehrswirtschaft Post-Logistik Telekommunikation (BG Verkehr), 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns.siguv.de.
    #13

Nameservers

warn

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
hns1.mcs.de 147.78.89.172NOERROR, 12 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.3
hns1.mcs.de 2a09:2040:0:10::10NOERROR, 12 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.3
hns2.mcs.de 162.19.245.172NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.3
hns2.mcs.de 2001:41d0:701:1100::4284NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.3
ns.siguv.de 193.104.3.200NOERROR, 6 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 5 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: hns1.mcs.de: "PowerDNS Authoritative Server 4.5.3"; hns2.mcs.de: "PowerDNS Authoritative Server 4.5.3". 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 268 · primary ns.siguv.de

Found

Primary (MNAME)
ns.siguv.de
Contact (RNAME)
dns.siguv.de
Serial
268
Refresh / retry
10800 s / 3600 s
Expire
2419200 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
hns1.mcs.de (147.78.89.172)268
hns1.mcs.de (2a09:2040:0:10::10)268
hns2.mcs.de (162.19.245.172)268
hns2.mcs.de (2001:41d0:701:1100::4284)268
ns.siguv.de (193.104.3.200)268

Checks

  • ✓ Serial 268 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 28d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.siguv.de is one of the listed nameservers.
  • ✓ Contact dns@siguv.de #25
    The SOA RNAME dns.siguv.de means dns@siguv.de.
  • ✓ Counter serial #26
    The serial 268 is a plain counter.

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

14 records at the apex

Found

Read from
147.78.89.172:53
TypeValueTTL
SOAns.siguv.de. dns.siguv.de. 268 10800 3600 2419200 900300
NShns1.mcs.de.300
NSns.siguv.de.300
NShns2.mcs.de.300
A193.104.3.59300
MX20 mail107b.cnuv.de.300
MX10 mail107a.cnuv.de.300
TXT"swisssign-check=1APrDUKovzqrdNLyqN2NqEKmOYg"300
TXT"google-site-verification=CAVsUNJdQOmwfGcG1yKGoMAkcG44cKR2b5T9Mu7Iz6I"300
TXT"v=spf1 include:_spf.cnuv.de include:_spf.zimpel.de ip4:193.104.3.0/24 -all"300
TXT"adobe-idp-site-verification=fd0583d87604249efd861e1028b232385114bab13f2fc52db0d2a7eb5ed82572"300
TXT"cisco-ci-domain-verification=7442d2f70a8f85096a15b07e91debde348a03e425bc8844391c25a980fdef7a2"300
TXT"MS=555E21E65C5D36AB2FB51F532B81F37265D69682"300
TXT"apple-domain-verification=EGgqfr7dDERQX67L"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.
  • ✓ 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