schauinsland-reisen.de

Checked 22 October 2026, 00:01 UTC · via 8.8.8.8
!Passed with warnings
19 passed 2 warnings 0 failed 8 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.dts-online.net, ns2.dts-online.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.dts-online.net, ns2.dts-online.net
NS in the zone
ns1.dts-online.net, ns2.dts-online.net
NameserverAddressesNetwork (AS)Glue
ns1.dts-online.net84.201.73.35 2a00:1348:0:1:23::1AS8879 DTS-Systeme - DTS Systeme GmbH, DE AS8879 DTS-Systeme - DTS Systeme GmbH, DE-
ns2.dts-online.net212.62.68.35 2a00:1348::23:0:0:1AS8879 DTS-Systeme - DTS Systeme GmbH, DE AS8879 DTS-Systeme - DTS Systeme GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dts-online.net, ns2.dts-online.net.
    #6
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a00:1348::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8879 (DTS-Systeme - DTS Systeme GmbH, DE): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    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
ns1.dts-online.net 84.201.73.35NOERROR, 11 ms, authoritativenoyes / yesrefusedFelix' DNS Server V0.1 <script>alert('hello, world');</script>
ns1.dts-online.net 2a00:1348:0:1:23::1NOERROR, 10 ms, authoritativenoyes / yesrefusedFelix' DNS Server V0.1 <script>alert('hello, world');</script>
ns2.dts-online.net 212.62.68.35NOERROR, 11 ms, authoritativenoyes / yesrefusedFelix' DNS Server V0.1\\x00%p%s
ns2.dts-online.net 2a00:1348::23:0:0:1NOERROR, 10 ms, authoritativenoyes / yesrefusedFelix' DNS Server V0.1\\x00%p%s

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: ns1.dts-online.net: "Felix' DNS Server V0.1 <script>alert('hello, world');</script>"; ns2.dts-online.net: "Felix' DNS Server V0.1\\\\x00%p%s". 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 2026102100 · primary ns1.dts-online.net

Found

Primary (MNAME)
ns1.dts-online.net
Contact (RNAME)
hostmaster.dts-online.net
Serial
2026102100
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
2560 s

Serial per nameserver

NameserverSerial
ns1.dts-online.net (84.201.73.35)2026102100
ns1.dts-online.net (2a00:1348:0:1:23::1)2026102100
ns2.dts-online.net (212.62.68.35)2026102100
ns2.dts-online.net (2a00:1348::23:0:0:1)2026102100

Checks

  • ✓ Serial 2026102100 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 42m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dts-online.net is one of the listed nameservers.
  • ✓ Contact hostmaster@dts-online.net #25
    The SOA RNAME hostmaster.dts-online.net means hostmaster@dts-online.net.
  • ✓ Date-based serial #26
    The serial 2026102100 follows the YYYYMMDDnn convention (2026-10-21).

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

20 records at the apex

Found

Read from
84.201.73.35:53
TypeValueTTL
SOAns1.dts-online.net. hostmaster.dts-online.net. 2026102100 16384 2048 1048576 2560300
NSns1.dts-online.net.300
NSns2.dts-online.net.300
A63.177.43.1683600
A3.125.229.133600
MX20 mx02.hornetsecurity.com.300
MX40 mx04.hornetsecurity.com.300
MX10 mx01.hornetsecurity.com.300
MX30 mx03.hornetsecurity.com.300
TXT"7347d1e53893bdbb98cb5c0e7fd9ccca2db3b82abe7344d1bbf8767398a5"3600
TXT"facebook-domain-verification=fkq022yum8bdbdil9i4f1df2b0gy4p"3600
TXT"google-site-verification=5dliV2OuypGGkqBJbZOdi7vxLxb9JjrNI1RUfSrJSBE"3600
TXT"swisssign-check=Ac5NBksHPcolHrv3H2UArdwymwU"3600
TXT"adobe-idp-site-verification=12a522dea651ee936451381a2e9eabeef33904e61d9a52637cf1e0246fc537ff"3600
TXT"MS=ms27231857"3600
TXT"google-site-verification=V_YOIy-iXrOiOx5mpSzUuBQydc0fB0f4QgEwAhnXZRg"3600
TXT"v=spf1 include:spf.schauinsland-reisen.de include:spfo365.schauinsland-reisen.de include:spf.hornetsecurity.com -all"3600
TXT"pinterest-site-verification=256443ea8fc60aaf46ea9b803a2e916f"3600
TXT"anthropic-domain-verification-a62dfw=OsvuhOStzWXybSjZpy5ddHAR7"3600
TXT"mLOTNrChIMfhcBER/wARbFx//nZWc8vP+Wz8jjKfCTgcC7ngGmgAOjMqdhFiHCX8obMdXpJQuUbcRd/jlPlbJw=="3600

Checks

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