mainchat.de

Checked 21 October 2026, 23:21 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 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.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.net
NS in the zone
ns1.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.net
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.eu176.97.158.21 2001:67c:10b8::21AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns3.domainoffensive.net192.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.eu, ns3.domainoffensive.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 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
  • ✓ Nameserver names under 3 TLDs #12
    Nameserver names use the TLDs .de, .eu, .net.
  • ✓ 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, 8 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.domainoffensive.eu 176.97.158.21NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.domainoffensive.eu 2001:67c:10b8::21NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns3.domainoffensive.net 192.174.68.20NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns3.domainoffensive.net 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.eu: "reg-wie1"; ns3.domainoffensive.net: "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

pass

serial 1789431859 · primary ns1.domainoffensive.de

Found

Primary (MNAME)
ns1.domainoffensive.de
Contact (RNAME)
info.domains.resellerinterface.de
Serial
1789431859
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

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

Checks

  • ✓ Serial 1789431859 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 15m.
  • ✓ 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 1789431859 is a Unix timestamp (2026-09-15 00:24 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

info

10 records at the apex

Found

Read from
192.174.68.21:53
TypeValueTTL
SOAns1.domainoffensive.de. info.domains.resellerinterface.de. 1789431859 14400 3600 604800 90086400
NSns1.domainoffensive.de.86400
NSns2.domainoffensive.eu.86400
NSns3.domainoffensive.net.86400
A116.202.9.166900
A116.202.21.136900
A116.203.213.72900
AAAA2a01:4f8:c17:c19c::1900
AAAA2a01:4f8:c2c:abf5::1900
AAAA2a01:4f8:c010:3f9c::1900

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, AAAA 15m, NS 1d.
  • ✓ 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