jugendherberge.de

Checked 21 October 2026, 23:01 UTC · via 8.8.8.8
✗Problems found
22 passed 1 warning 1 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

ns1.djh-rechenzentrum.de, ns1.vegasystems.de, ns2.vegasystems.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.djh-rechenzentrum.de, ns1.vegasystems.de, ns2.vegasystems.net
NS in the zone
ns1.djh-rechenzentrum.de, ns1.vegasystems.de, ns2.vegasystems.net
NameserverAddressesNetwork (AS)Glue
ns1.djh-rechenzentrum.de80.70.184.6AS34372 vegasystems-as - VegaSystems GmbH & Co. KG, DE80.70.184.6
ns1.vegasystems.de80.70.176.1 2a02:450:0:1::10AS34372 vegasystems-as - VegaSystems GmbH & Co. KG, DE AS34372 vegasystems-as - VegaSystems GmbH & Co. KG, DE80.70.176.1 2a02:450:0:1::10
ns2.vegasystems.net194.145.124.86 2001:67c:2104:ff02::86AS9182 comspaceAS - COMSPACE GmbH & Co KG, DE AS9182 comspaceAS - COMSPACE GmbH & Co KG, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.djh-rechenzentrum.de, ns1.vegasystems.de, ns2.vegasystems.net.
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS34372 (vegasystems-as - VegaSystems GmbH & Co. KG, DE): 3 addresses; AS9182 (comspaceAS - COMSPACE GmbH & Co KG, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.djh-rechenzentrum.de.
    #13

Nameservers

fail

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.djh-rechenzentrum.de 80.70.184.6NOERROR, 12 ms, authoritativenono / yesrefused-
ns1.vegasystems.de 80.70.176.1NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns1.vegasystems.de 2a02:450:0:1::10NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.vegasystems.net 194.145.124.86NOERROR, 26 ms, authoritativenoyes / yesrefused-
ns2.vegasystems.net 2001:67c:2104:ff02::86NOERROR, 27 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.djh-rechenzentrum.de (80.70.184.6): dial tcp 80.70.184.6:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026101314 · primary ns1.vegasystems.de

Found

Primary (MNAME)
ns1.vegasystems.de
Contact (RNAME)
hostmaster.vegasystems.de
Serial
2026101314
Refresh / retry
36000 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.djh-rechenzentrum.de (80.70.184.6)2026101314
ns1.vegasystems.de (80.70.176.1)2026101314
ns1.vegasystems.de (2a02:450:0:1::10)2026101314
ns2.vegasystems.net (194.145.124.86)2026101314
ns2.vegasystems.net (2001:67c:2104:ff02::86)2026101314

Checks

  • ✓ Serial 2026101314 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 10h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.vegasystems.de is one of the listed nameservers.
  • ✓ Contact hostmaster@vegasystems.de #25
    The SOA RNAME hostmaster.vegasystems.de means hostmaster@vegasystems.de.
  • ✓ Date-based serial #26
    The serial 2026101314 follows the YYYYMMDDnn convention (2026-10-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

15 records at the apex

Found

Read from
80.70.184.6:53
TypeValueTTL
SOAns1.vegasystems.de. hostmaster.vegasystems.de. 2026101314 36000 3600 604800 8640021600
NSns2.vegasystems.net.21600
NSns1.vegasystems.de.21600
NSns1.djh-rechenzentrum.de.21600
A217.7.141.151300
MX30 mx03.hornetsecurity.com.3600
MX20 mx02.hornetsecurity.com.3600
MX40 mx04.hornetsecurity.com.3600
MX10 mx01.hornetsecurity.com.3600
TXT"apple-domain-verification=cD7clmdb12wRtL2e"3600
TXT"google-site-verification=MEUimIeX4op9vrP1lAnVxuWjmVv2VdeuP0C3ApywP58"3600
TXT"MS=ms54130884"3600
TXT"0912b748832443b7a005f361417051f6"3600
TXT"+VyQRdwHwg2ooCKflbTUeiXr2vQ15TxSFRxd+XlU2rH4qMj4lqQ/zYLS+hdjq72EUI+5HqK89n6k4NvKfTjuSQ=="3600
TXT"v=spf1 ip4:194.25.238.4/32 include:spf.jugendherberge.de include:spf.protection.outlook.com ip4:62.153.87.85/32 ip4:185.57.242.9/32 include:spf.hornetsecurity.com -all"3600

Checks

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