metager.de

Checked 21 October 2026, 23:22 UTC · via 8.8.8.8
iAll checks passed
28 passed 0 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

pass

ns.inwx.de, ns2.inwx.de, ns3.inwx.eu

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.inwx.de, ns2.inwx.de, ns3.inwx.eu
NS in the zone
ns.inwx.de, ns2.inwx.de, ns3.inwx.eu
NameserverAddressesNetwork (AS)Glue
ns.inwx.de192.174.68.104 2001:67c:1bc::104AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.inwx.de176.97.158.104 2001:67c:10b8::104AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns3.inwx.eu45.87.158.53 2a02:d500::53AS48596 INWX - InterNetworX Management GmbH, DE AS48596 INWX - InterNetworX Management GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.inwx.de, ns2.inwx.de, ns3.inwx.eu.
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses; AS48596 (INWX - InterNetworX Management GmbH, DE): 2 addresses.
  • ✓ 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
ns.inwx.de 192.174.68.104NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns.inwx.de 2001:67c:1bc::104NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.inwx.de 176.97.158.104NOERROR, 11 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.inwx.de 2001:67c:10b8::104NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns3.inwx.eu 45.87.158.53NOERROR, 12 ms, authoritativenoyes / yesrefusedINWX AXFR Server
ns3.inwx.eu 2a02:d500::53NOERROR, 12 ms, authoritativenoyes / yesrefusedINWX AXFR Server

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: ns.inwx.de: "RcodeZero DNS"; ns2.inwx.de: "reg-wie1"; ns3.inwx.eu: "INWX AXFR Server".
    #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 2026091700 · primary ns.inwx.de

Found

Primary (MNAME)
ns.inwx.de
Contact (RNAME)
hostmaster.inwx.de
Serial
2026091700
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.inwx.de (192.174.68.104)2026091700
ns.inwx.de (2001:67c:1bc::104)2026091700
ns2.inwx.de (176.97.158.104)2026091700
ns2.inwx.de (2001:67c:10b8::104)2026091700
ns3.inwx.eu (45.87.158.53)2026091700
ns3.inwx.eu (2a02:d500::53)2026091700

Checks

  • ✓ Serial 2026091700 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.inwx.de is one of the listed nameservers.
  • ✓ Contact hostmaster@inwx.de #25
    The SOA RNAME hostmaster.inwx.de means hostmaster@inwx.de.
  • ✓ Date-based serial #26
    The serial 2026091700 follows the YYYYMMDDnn convention (2026-09-17).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
62586ECDSAP256SHA256 (13)SHA256 542A6C0FDD1160BB…yes

DNSKEY in the zone

Key tagRoleAlgorithm
62586KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 62586 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

8 records at the apex

Found

Read from
192.174.68.104:53
TypeValueTTL
SOAns.inwx.de. hostmaster.inwx.de. 2026091700 10800 3600 604800 360086400
NSns.inwx.de.86400
NSns2.inwx.de.86400
NSns3.inwx.eu.86400
A49.12.118.386400
AAAA2a01:4f8:1c0c:80f3::186400
MX10 mx.metager.de.86400
TXT"v=spf1 a:smtp1.metager.de a:smtp2.metager.de a:smtp3.metager.de ~all"86400

Checks

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