netcup.de

Checked 21 October 2026, 23:31 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 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

acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems
NS in the zone
acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems
NameserverAddressesNetwork (AS)Glue
acns01.xaas.systems217.146.18.1 2a00:11c0:aa1::1AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT-
acns02.xaas.systems188.172.248.1 2a05:8900:aa1::1AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT-
acns03.xaas.systems213.227.160.1 2605:380:aa1::1AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT-
acns04.xaas.systems213.227.191.1 2803:ad80:aa1::1AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT-
acns05.xaas.systems185.81.208.1 2a00:11c0:1010::1AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT AS42388 ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT-

Checks

  • ✓ 5 nameservers #6
    Delegated to acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems.
  • ✓ 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 5 IPv4 /24s and 5 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS42388 (ANX-CLOUDDNS - Anexia Cloud Solutions GmbH, AT): 10 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 .systems
    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

pass

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
acns01.xaas.systems 217.146.18.1NOERROR, 3 ms, authoritativenoyes / yesrefused-
acns01.xaas.systems 2a00:11c0:aa1::1NOERROR, 8 ms, authoritativenoyes / yesrefused-
acns02.xaas.systems 188.172.248.1NOERROR, 8 ms, authoritativenoyes / yesrefused-
acns02.xaas.systems 2a05:8900:aa1::1NOERROR, 8 ms, authoritativenoyes / yesrefused-
acns03.xaas.systems 213.227.160.1NOERROR, 8 ms, authoritativenoyes / yesrefused-
acns03.xaas.systems 2605:380:aa1::1NOERROR, 8 ms, authoritativenoyes / yesrefused-
acns04.xaas.systems 213.227.191.1NOERROR, 8 ms, authoritativenoyes / yesrefused-
acns04.xaas.systems 2803:ad80:aa1::1NOERROR, 7 ms, authoritativenoyes / yesrefused-
acns05.xaas.systems 185.81.208.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
acns05.xaas.systems 2a00:11c0:1010::1NOERROR, 7 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 10 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 26 · primary root-dns.netcup.net

Found

Primary (MNAME)
root-dns.netcup.net
Contact (RNAME)
dnsadmin.netcup.net
Serial
26
Refresh / retry
28800 s / 7200 s
Expire
1209600 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
acns01.xaas.systems (217.146.18.1)26
acns01.xaas.systems (2a00:11c0:aa1::1)26
acns02.xaas.systems (188.172.248.1)26
acns02.xaas.systems (2a05:8900:aa1::1)26
acns03.xaas.systems (213.227.160.1)26
acns03.xaas.systems (2605:380:aa1::1)26
acns04.xaas.systems (213.227.191.1)26
acns04.xaas.systems (2803:ad80:aa1::1)26
acns05.xaas.systems (185.81.208.1)26
acns05.xaas.systems (2a00:11c0:1010::1)26

Checks

  • ✓ Serial 26 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 14d, negative TTL 2h.
  • i
    Hidden master
    The primary nameserver root-dns.netcup.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 dnsadmin@netcup.net #25
    The SOA RNAME dnsadmin.netcup.net means dnsadmin@netcup.net.
  • ✓ Counter serial #26
    The serial 26 is a plain counter.

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

12 records at the apex

Found

Read from
217.146.18.1:53
TypeValueTTL
SOAroot-dns.netcup.net. dnsadmin.netcup.net. 26 28800 7200 1209600 72007200
NSacns02.xaas.systems.7200
NSacns03.xaas.systems.7200
NSacns01.xaas.systems.7200
NSacns05.xaas.systems.7200
NSacns04.xaas.systems.7200
A46.38.224.307200
AAAA2a03:4000::e01e7200
MX20 backupmx-fra1.netcup.net.7200
MX10 smtp.netcup.net.7200
TXT"google-site-verification=XDly02N5dgwwk-oPdSjsfchNFpV-jyDfUl45Vd75NIg"7200
TXT"v=spf1 ip4:46.38.225.170 ip4:212.123.34.96/28 ip4:212.123.36.25 ip4:188.65.77.204 ip6:2a03:4000:0:1::e1aa mx ip4:212.123.41.224/28 ip4:45.132.63.68 include:_spf.hostedemail.com include:spf.cloudpowered.email -all"7200

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, AAAA 2h, MX 2h, NS 2h. The NS TTL at the parent is 1d and in the zone 2h; 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