fes.de

Checked 21 October 2026, 22:20 UTC · via 8.8.8.8
✗Problems found
17 passed 2 warnings 2 failed 8 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

ns.fes.de, ns2.fes.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.fes.de, ns2.fes.de
NS in the zone
ns.fes.de, ns2.fes.de, pns.dtag.de
NameserverAddressesNetwork (AS)Glue
ns.fes.de195.243.222.10AS3320 DTAG - Deutsche Telekom AG, DE195.243.222.10
ns2.fes.de80.150.83.154AS3320 DTAG - Deutsche Telekom AG, DE80.150.83.154
pns.dtag.de (zone only)194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.fes.de, ns2.fes.de.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: pns.dtag.de. ns.fes.de, ns2.fes.de report NS ns.fes.de ns2.fes.de pns.dtag.de.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns.fes.de, ns2.fes.de.
  • ✓ 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 1 IPv6 /48.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS3320 (DTAG - Deutsche Telekom AG, DE): 4 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 .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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns.fes.de, ns2.fes.de.
    #13

Nameservers

fail

2 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.fes.de 195.243.222.10NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns2.fes.de 80.150.83.154NOERROR, 13 ms, authoritativenoyes / yesrefused-
pns.dtag.de 194.25.0.125REFUSED, 9 ms, NOT authoritativenono / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100REFUSED, 10 ms, NOT authoritativenono / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 4 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: pns.dtag.de (194.25.0.125): REFUSED, authoritative=false; pns.dtag.de (2003:40:8000::100): REFUSED, authoritative=false.
    #15
  • ✓ 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: pns.dtag.de: "DomainNameServer".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: pns.dtag.de (194.25.0.125): ; pns.dtag.de (2003:40:8000::100): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 817 · primary ns.fes.de

Found

Primary (MNAME)
ns.fes.de
Contact (RNAME)
hostmaster.fes.de
Serial
817
Refresh / retry
86400 s / 10800 s
Expire
691200 s
Negative TTL
3000 s

Serial per nameserver

NameserverSerial
ns.fes.de (195.243.222.10)817
ns2.fes.de (80.150.83.154)817

Checks

  • ✓ Serial 817 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 3h, expire 8d, negative TTL 50m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.fes.de is one of the listed nameservers.
  • ✓ Contact hostmaster@fes.de #25
    The SOA RNAME hostmaster.fes.de means hostmaster@fes.de.
  • ✓ Counter serial #26
    The serial 817 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

10 records at the apex

Found

Read from
195.243.222.10:53
TypeValueTTL
SOAns.fes.de. hostmaster.fes.de. 817 86400 10800 691200 30003600
NSpns.dtag.de.3000
NSns2.fes.de.3000
NSns.fes.de.3000
A195.243.222.303000
MX10 mail1.fes.de.3000
TXT"_globalsign-domain-verification=g9678m9d289s32mqoo2jsicdbp"3000
TXT"apple-domain-verification=N4bfRgMeT6JrrMA5"3000
TXT"g9678m9d289s32mqoo2jsicdbp"3000
TXT"v=spf1 ip4:195.243.222.11 ip4:195.243.222.33 ip4:195.243.222.75 ip4:195.243.222.80/28 ip4:195.243.222.95 -all"3000

Checks

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