dachau.de

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

ns1.sasg.de, ns1.sasg.eu, ns2.sasg.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.sasg.de, ns1.sasg.eu, ns2.sasg.de
NS in the zone
ns1.sasg.de, ns1.sasg.eu, ns2.sasg.de
NameserverAddressesNetwork (AS)Glue
ns1.sasg.de95.142.65.23 2a00:1100:fe:53::23AS51483 SASG - SaSG GmbH & Co. KG, DE AS51483 SASG - SaSG GmbH & Co. KG, DE95.142.65.23 2a00:1100:fe:53::23
ns1.sasg.eu185.74.224.115 2a00:1100:700:2::115AS51483 SASG - SaSG GmbH & Co. KG, DE AS51483 SASG - SaSG GmbH & Co. KG, DE-
ns2.sasg.de95.142.67.23 2a00:1100:ff:53::23AS51483 SASG - SaSG GmbH & Co. KG, DE AS51483 SASG - SaSG GmbH & Co. KG, DE95.142.67.23 2a00:1100:ff:53::23

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.sasg.de, ns1.sasg.eu, ns2.sasg.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 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS51483 (SASG - SaSG GmbH & Co. KG, DE): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .eu.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sasg.de 95.142.65.23NOERROR, 11 ms, authoritativenoyes / yesrefusedSaSG DNS authdns1-1
ns1.sasg.de 2a00:1100:fe:53::23NOERROR, 11 ms, authoritativenoyes / yesrefusedSaSG DNS authdns1-1
ns1.sasg.eu 185.74.224.115NOERROR, 10 ms, authoritativenoyes / yesrefusedSaSG DNS
ns1.sasg.eu 2a00:1100:700:2::115NOERROR, 11 ms, authoritativenoyes / yesrefusedSaSG DNS
ns2.sasg.de 95.142.67.23NOERROR, 11 ms, authoritativenoyes / yesrefusedSaSG DNS
ns2.sasg.de 2a00:1100:ff:53::23NOERROR, 12 ms, authoritativenoyes / yesrefusedSaSG DNS

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.sasg.de: "SaSG DNS authdns1-1"; ns1.sasg.eu: "SaSG DNS"; ns2.sasg.de: "SaSG DNS".
    #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

warn

serial 2026100202 · primary ns1.sasg.de

Found

Primary (MNAME)
ns1.sasg.de
Contact (RNAME)
hostmaster.sasg.net
Serial
2026100202
Refresh / retry
60 s / 300 s
Expire
604800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.sasg.de (95.142.65.23)2026100202
ns1.sasg.de (2a00:1100:fe:53::23)2026100202
ns1.sasg.eu (185.74.224.115)2026100202
ns1.sasg.eu (2a00:1100:700:2::115)2026100202
ns2.sasg.de (95.142.67.23)2026100202
ns2.sasg.de (2a00:1100:ff:53::23)2026100202

Checks

  • ✓ Serial 2026100202 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 1m is outside 20m–1d; retry 5m should be shorter than refresh 1m; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1m, retry 5m, expire 7d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.sasg.de is one of the listed nameservers.
  • ✓ Contact hostmaster@sasg.net #25
    The SOA RNAME hostmaster.sasg.net means hostmaster@sasg.net.
  • ✓ Date-based serial #26
    The serial 2026100202 follows the YYYYMMDDnn convention (2026-10-02).

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

warn

16 records at the apex

Found

Read from
95.142.65.23:53
TypeValueTTL
SOAns1.sasg.de. hostmaster.sasg.net. 2026100202 60 300 604800 6060
NSns2.sasg.de.60
NSns1.sasg.eu.60
NSns1.sasg.de.60
A46.225.253.22060
MX10 mail.bayern.de.60
TXT"MS=0418B40EFB6027C4DBBDA2A596043B02ABC38201"60
TXT"REDDCRYPT=66d9893d46246637e2e015e3"60
TXT"v=spf1 ip4:195.200.70.64/26 ip4:46.31.222.208/28 ip4:82.135.28.23 ip4:95.142.66.126 ip4:46.235.112.22 a:otc-de-spf.mms.t-systems-service.com -all"60
TXT"1password-site-verification=ALLBMUDAYNALZBUCFVZLZPKCCU"60
TXT"prowise-site-verification=8c85bc8a460cf80fc0a4cc7dac192ba8d8498b85"60
TXT"google-site-verification=km5sUlUZNffqUxs7myGB-Ux-AFwKmVukmGtcfPqYVlI"60
TXT"apple-domain-verification=HoHnts36HcKmv4ro"60
TXT"brevo-code:d37131aae7a0a5dca44dd6d722ec0d3f"60
TXT"a78d0e9e92f167f93cb66ba177575633660ccd8f0608d655dbba69380120961d"60
TXT"ms75243365"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; resolvers may use either.
    #32
  • ✓ 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