sozialgerichtsbarkeit.de

Checked 22 October 2026, 00:23 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 0 failed 7 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.domainoffensive.de, ns2.domainoffensive.de, ns3.domainoffensive.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.domainoffensive.de, ns2.domainoffensive.de, ns3.domainoffensive.de
NS in the zone
ns1.domainoffensive.de, ns2.domainoffensive.de, ns3.domainoffensive.de
NameserverAddressesNetwork (AS)Glue
ns1.domainoffensive.de192.174.68.21 2001:67c:1bc::21AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.domainoffensive.de176.97.158.21 2001:67c:10b8::21AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns3.domainoffensive.de192.174.68.20 2001:67c:1bc::20AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.domainoffensive.de, ns2.domainoffensive.de, ns3.domainoffensive.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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 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
  • 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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.domainoffensive.de 192.174.68.21NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.domainoffensive.de 2001:67c:1bc::21NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.domainoffensive.de 176.97.158.21NOERROR, 11 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.domainoffensive.de 2001:67c:10b8::21NOERROR, 11 ms, authoritativenoyes / yesrefusedreg-wie1
ns3.domainoffensive.de 192.174.68.20NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns3.domainoffensive.de 2001:67c:1bc::20NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero 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.domainoffensive.de: "RcodeZero DNS"; ns2.domainoffensive.de: "reg-wie1"; ns3.domainoffensive.de: "RcodeZero 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 1758799603 · primary ns1.domainoffensive.de

Found

Primary (MNAME)
ns1.domainoffensive.de
Contact (RNAME)
info.domains.resellerinterface.de
Serial
1758799603
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
120 s

Serial per nameserver

NameserverSerial
ns1.domainoffensive.de (192.174.68.21)1758799603
ns1.domainoffensive.de (2001:67c:1bc::21)1758799603
ns2.domainoffensive.de (176.97.158.21)1758799603
ns2.domainoffensive.de (2001:67c:10b8::21)1758799603
ns3.domainoffensive.de (192.174.68.20)1758799603
ns3.domainoffensive.de (2001:67c:1bc::20)1758799603

Checks

  • ✓ Serial 1758799603 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 2m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.domainoffensive.de is one of the listed nameservers.
  • ✓ Contact info@domains.resellerinterface.de #25
    The SOA RNAME info.domains.resellerinterface.de means info@domains.resellerinterface.de.
  • ✓ Timestamp serial #26
    The serial 1758799603 is a Unix timestamp (2025-09-25 11:26 UTC).

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

6 records at the apex

Found

Read from
192.174.68.21:53
TypeValueTTL
SOAns1.domainoffensive.de. info.domains.resellerinterface.de. 1758799603 10800 3600 604800 12086400
NSns1.domainoffensive.de.86400
NSns2.domainoffensive.de.86400
NSns3.domainoffensive.de.86400
A188.245.241.57120
MX10 mail.sozialgerichtsbarkeit.de.120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), MX (2m). Low TTLs are useful just before a planned change.
    #32
  • ✓ 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