wolfsburg.de

Checked 22 October 2026, 01:01 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 4 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.wobcom.de, ns2.wobcom.de, ns3.wobcom.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.wobcom.de, ns2.wobcom.de, ns3.wobcom.de
NS in the zone
ns1.wobcom.de, ns2.wobcom.de, ns3.wobcom.de
NameserverAddressesNetwork (AS)Glue
ns1.wobcom.de62.176.224.83 2a01:580::30:83AS9136 WOBCOM - Wobcom GmbH, DE AS9136 WOBCOM - Wobcom GmbH, DE62.176.224.83 2a01:580::30:83
ns2.wobcom.de62.176.224.84 2a01:580::30:84AS9136 WOBCOM - Wobcom GmbH, DE AS9136 WOBCOM - Wobcom GmbH, DE62.176.224.84 2a01:580::30:84
ns3.wobcom.de188.245.238.211 2a01:4f8:c013:a194::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE188.245.238.211 2a01:4f8:c013:a194::1

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.wobcom.de, ns2.wobcom.de, ns3.wobcom.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 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS9136 (WOBCOM - Wobcom GmbH, DE): 4 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

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.wobcom.de 62.176.224.83NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.5
ns1.wobcom.de 2a01:580::30:83NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.5
ns2.wobcom.de 62.176.224.84NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.5
ns2.wobcom.de 2a01:580::30:84NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.5
ns3.wobcom.de 188.245.238.211NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.5
ns3.wobcom.de 2a01:4f8:c013:a194::1NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.5

Checks

  • ✓ All respond #14
    All 6 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.wobcom.de: "PowerDNS Authoritative Server 5.0.5"; ns2.wobcom.de: "PowerDNS Authoritative Server 5.0.5"; ns3.wobcom.de: "PowerDNS Authoritative Server 5.0.5". 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 2019061303 · primary ns1.wobcom.de

Found

Primary (MNAME)
ns1.wobcom.de
Contact (RNAME)
noc.wobcom.de
Serial
2019061303
Refresh / retry
10800 s / 1800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.wobcom.de (62.176.224.83)2019061303
ns1.wobcom.de (2a01:580::30:83)2019061303
ns2.wobcom.de (62.176.224.84)2019061303
ns2.wobcom.de (2a01:580::30:84)2019061303
ns3.wobcom.de (188.245.238.211)2019061303
ns3.wobcom.de (2a01:4f8:c013:a194::1)2019061303

Checks

  • ✓ Serial 2019061303 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.wobcom.de is one of the listed nameservers.
  • ✓ Contact noc@wobcom.de #25
    The SOA RNAME noc.wobcom.de means noc@wobcom.de.
  • ✓ Date-based serial #26
    The serial 2019061303 follows the YYYYMMDDnn convention (2019-06-13).

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

10 records at the apex

Found

Read from
62.176.224.83:53
TypeValueTTL
SOAns1.wobcom.de. noc.wobcom.de. 2019061303 10800 1800 604800 360010800
NSns1.wobcom.de.3600
NSns2.wobcom.de.3600
NSns3.wobcom.de.3600
A62.176.236.423600
A62.176.236.413600
MX10 mx.wobcom.de.3600
TXT"postgate-verify=55e9a5e89a6a28b4bdd383dc1982c059"300
TXT"MS=A96C1D870EDBF5B8C30B256459226AD6862D26AD"300
TXT"v=spf1 redirect=_spf.wobcom.de"300

Checks

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