abacho.de

Checked 21 October 2026, 21:27 UTC · via 8.8.8.8
✗Problems found
20 passed 1 warning 1 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.eu.rrpproxy.net, ns1.na.rrpproxy.net, ns2.eu.rrpproxy.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.eu.rrpproxy.net, ns1.na.rrpproxy.net, ns2.eu.rrpproxy.net
NS in the zone
ns1.eu.rrpproxy.net, ns1.na.rrpproxy.net, ns2.eu.rrpproxy.net
NameserverAddressesNetwork (AS)Glue
ns1.eu.rrpproxy.net193.227.117.227 2a04:2b00:14cc::227AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns1.na.rrpproxy.net193.227.117.228 2a04:2b00:14cc::228AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.eu.rrpproxy.net194.50.187.227 2a04:2b00:14dd::227AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.eu.rrpproxy.net, ns1.na.rrpproxy.net, ns2.eu.rrpproxy.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
  • i
    All nameserver names under .net
    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

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.eu.rrpproxy.net 193.227.117.227NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.eu.rrpproxy.net 2a04:2b00:14cc::227NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.na.rrpproxy.net 193.227.117.228NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.na.rrpproxy.net 2a04:2b00:14cc::228NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.eu.rrpproxy.net 194.50.187.227NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.eu.rrpproxy.net 2a04:2b00:14dd::227no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns2.eu.rrpproxy.net (2a04:2b00:14dd::227): read udp [2a01:4f8:1c1c:eebf::1]:60673->[2a04:2b00:14dd::227]:53: i/o timeout.
    #14
  • ✓ 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.eu.rrpproxy.net: "RcodeZero DNS"; ns1.na.rrpproxy.net: "RcodeZero DNS"; ns2.eu.rrpproxy.net: "reg-wie1".
    #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

info

serial 2022031403 · primary ns1.rrpproxy.net

Found

Primary (MNAME)
ns1.rrpproxy.net
Contact (RNAME)
tech.rrpproxy.net
Serial
2022031403
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
28800 s

Serial per nameserver

NameserverSerial
ns1.eu.rrpproxy.net (193.227.117.227)2022031403
ns1.eu.rrpproxy.net (2a04:2b00:14cc::227)2022031403
ns1.na.rrpproxy.net (193.227.117.228)2022031403
ns1.na.rrpproxy.net (2a04:2b00:14cc::228)2022031403
ns2.eu.rrpproxy.net (194.50.187.227)2022031403

Checks

  • ✓ Serial 2022031403 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 8h.
  • i
    Hidden master
    The primary nameserver ns1.rrpproxy.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact tech@rrpproxy.net #25
    The SOA RNAME tech.rrpproxy.net means tech@rrpproxy.net.
  • ✓ Date-based serial #26
    The serial 2022031403 follows the YYYYMMDDnn convention (2022-03-14).

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

4 records at the apex

Found

Read from
193.227.117.227:53
TypeValueTTL
SOAns1.rrpproxy.net. tech.rrpproxy.net. 2022031403 10800 3600 604800 2880028800
NSns1.eu.rrpproxy.net.172800
NSns1.na.rrpproxy.net.172800
NSns2.eu.rrpproxy.net.172800

Checks

  • ✓ TTLs within range #32
    TTLs: NS 2d. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
  • ✓ 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