fussballmanager.de

Checked 21 October 2026, 22:32 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 1 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

warn

ns1.ns-network.org, ns2.ns-network.org, ns3.ns-network.org

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ns-network.org, ns2.ns-network.org, ns3.ns-network.org
NS in the zone
ns1.ns-network.org, ns2.ns-network.org, ns3.ns-network.org
NameserverAddressesNetwork (AS)Glue
ns1.ns-network.org91.99.233.220AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.ns-network.org46.224.13.10AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns3.ns-network.org46.62.201.236AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.ns-network.org, ns2.ns-network.org, ns3.ns-network.org.
  • ✓ 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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 3 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 .org
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ns-network.org 91.99.233.220NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns2.ns-network.org 46.224.13.10NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns3.ns-network.org 46.62.201.236NOERROR, 25 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3

Checks

  • ✓ All respond #14
    All 3 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ns-network.org: "PowerDNS Authoritative Server 4.8.3"; ns2.ns-network.org: "PowerDNS Authoritative Server 4.8.3"; ns3.ns-network.org: "PowerDNS Authoritative Server 4.8.3". Hide or replace the version string.
    #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

fail

serial 2026052900 · primary ns1.ns-network.org

Found

Primary (MNAME)
ns1.ns-network.org
Contact (RNAME)
nowak\@idgv.info
Serial
2026052900
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.ns-network.org (91.99.233.220)2026052900
ns2.ns-network.org (46.224.13.10)2026052900
ns3.ns-network.org (46.62.201.236)2026052900

Checks

  • ✓ Serial 2026052900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ns-network.org is one of the listed nameservers.
  • ✗
    Invalid contact address
    The SOA RNAME "nowak\\@idgv.info" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • ✓ Date-based serial #26
    The serial 2026052900 follows the YYYYMMDDnn convention (2026-05-29).

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

7 records at the apex

Found

Read from
91.99.233.220:53
TypeValueTTL
SOAns1.ns-network.org. nowak\@idgv.info. 2026052900 28800 7200 604800 864003600
NSns1.ns-network.org.3600
NSns3.ns-network.org.3600
NSns2.ns-network.org.3600
A37.120.165.183600
MX10 mail.idgv.info.3600
TXT"v=spf1 a mx -all"3600

Checks

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