reclam.de

Checked 22 October 2026, 00:00 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 0 failed 6 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.plutex.de, ns2.plutex.de, ns3.plutex.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.plutex.de, ns2.plutex.de, ns3.plutex.de
NS in the zone
ns1.plutex.de, ns2.plutex.de, ns3.plutex.de
NameserverAddressesNetwork (AS)Glue
ns1.plutex.de91.202.40.53 2a02:16d0:0:1::53AS49855 PLUTEX - PLUTEX GmbH, DE AS49855 PLUTEX - PLUTEX GmbH, DE91.202.40.53 2a02:16d0:0:1::53
ns2.plutex.de91.202.41.53 2a02:16d0:0:1::1:53AS49855 PLUTEX - PLUTEX GmbH, DE AS49855 PLUTEX - PLUTEX GmbH, DE91.202.41.53 2a02:16d0:0:1::1:53
ns3.plutex.de116.203.36.144 2a01:4f8:c2c:df5b::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE116.203.36.144 2a01:4f8:c2c:df5b::1

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.plutex.de, ns2.plutex.de, ns3.plutex.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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS49855 (PLUTEX - PLUTEX GmbH, DE): 4 addresses.
  • 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.plutex.de 91.202.40.53NOERROR, 13 ms, authoritativenoyes / yesrefusedDNS Service
ns1.plutex.de 2a02:16d0:0:1::53NOERROR, 10 ms, authoritativenoyes / yesrefusedDNS Service
ns2.plutex.de 91.202.41.53NOERROR, 9 ms, authoritativenoyes / yesrefusedDNS Service
ns2.plutex.de 2a02:16d0:0:1::1:53NOERROR, 11 ms, authoritativenoyes / yesrefusedDNS Service
ns3.plutex.de 116.203.36.144NOERROR, 5 ms, authoritativenoyes / yesrefusedDNS Service
ns3.plutex.de 2a01:4f8:c2c:df5b::1NOERROR, 4 ms, authoritativenoyes / yesrefusedDNS Service

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.plutex.de: "DNS Service"; ns2.plutex.de: "DNS Service"; ns3.plutex.de: "DNS Service".
    #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 2026062201 · primary ns1.plutex.de

Found

Primary (MNAME)
ns1.plutex.de
Contact (RNAME)
tech.plutex.de
Serial
2026062201
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.plutex.de (91.202.40.53)2026062201
ns1.plutex.de (2a02:16d0:0:1::53)2026062201
ns2.plutex.de (91.202.41.53)2026062201
ns2.plutex.de (2a02:16d0:0:1::1:53)2026062201
ns3.plutex.de (116.203.36.144)2026062201
ns3.plutex.de (2a01:4f8:c2c:df5b::1)2026062201

Checks

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

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

16 records at the apex

Found

Read from
91.202.40.53:53
TypeValueTTL
SOAns1.plutex.de. tech.plutex.de. 2026062201 10800 3600 1209600 10800300
NSns1.plutex.de.300
NSns3.plutex.de.300
NSns2.plutex.de.300
A109.69.65.89300
AAAA2a02:16d0:1005:b600::1300
MX10 alt4.aspmx.l.google.com.300
MX10 alt3.aspmx.l.google.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
MX1 aspmx.l.google.com.300
TXT"MS=7C38CE2166EF1B8E9C3B187612F1B3916F56C25E"300
TXT"google-site-verification=ZbIC74lwnuWxSIvAwG5uGcVbvzMYl3zU7YKbuaX12iM"300
TXT"hubspot-oyV9Arf78UB1"300
TXT"_bqkbhwo65dgpvtrwoe5osnpjqmbrbc4"300
TXT"v=spf1 a mx ip4:109.69.65.89 ip6:2a02:16d0:1005:b600::1 include:ldgt1450mi.spf.dmarc.alfatier.io include:_spf.google.com include:servicemail24.de ip4:62.113.214.228 ip4:88.99.204.104 ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, 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