feg.de

Checked 21 October 2026, 22:20 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 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.feg.de, ns2.feg.de, ns3.feg.de, ns4.feg.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.feg.de, ns2.feg.de, ns3.feg.de, ns4.feg.de
NS in the zone
ns1.feg.de, ns2.feg.de, ns3.feg.de, ns4.feg.de
NameserverAddressesNetwork (AS)Glue
ns1.feg.de88.198.217.62AS24940 HETZNER-AS - Hetzner Online GmbH, DE88.198.217.62
ns2.feg.de95.129.54.23 2a00:17d8:100:1::c91AS48823 AS48823 - Hosting.de GmbH, DE AS12574 ROUTING - Hosting.de GmbH, DE95.129.54.23 2a00:17d8:100:1::c91
ns3.feg.de142.132.212.110 2a01:4f8:262:50cf::2222:53AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE142.132.212.110 2a01:4f8:262:50cf::2222:53
ns4.feg.de109.230.236.195 2a05:bec0:1:3::53AS197071 ACTIVE-SERVERS - active 1 GmbH, DE AS197071 ACTIVE-SERVERS - active 1 GmbH, DE109.230.236.195 2a05:bec0:1:3::53

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.feg.de, ns2.feg.de, ns3.feg.de, ns4.feg.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.feg.de, ns2.feg.de, ns3.feg.de, ns4.feg.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 4 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS12574 (ROUTING - Hosting.de GmbH, DE): 1 address; AS197071 (ACTIVE-SERVERS - active 1 GmbH, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 3 addresses; AS48823 (AS48823 - Hosting.de GmbH, DE): 1 address.
  • 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: ns1.feg.de.
    #13

Nameservers

warn

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.feg.de 88.198.217.62NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.8
ns2.feg.de 95.129.54.23NOERROR, 10 ms, authoritativenoyes / yesrefusednone of your business
ns2.feg.de 2a00:17d8:100:1::c91NOERROR, 9 ms, authoritativenoyes / yesrefusednone of your business
ns3.feg.de 142.132.212.110NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.8
ns3.feg.de 2a01:4f8:262:50cf::2222:53NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.8
ns4.feg.de 109.230.236.195NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.8
ns4.feg.de 2a05:bec0:1:3::53NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.8

Checks

  • ✓ All respond #14
    All 7 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.feg.de: "PowerDNS Authoritative Server 4.9.8"; ns3.feg.de: "PowerDNS Authoritative Server 4.9.8"; ns4.feg.de: "PowerDNS Authoritative Server 4.9.8". 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

pass

serial 2026101401 · primary ns1.feg.de

Found

Primary (MNAME)
ns1.feg.de
Contact (RNAME)
support.feg.de
Serial
2026101401
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.feg.de (88.198.217.62)2026101401
ns2.feg.de (95.129.54.23)2026101401
ns2.feg.de (2a00:17d8:100:1::c91)2026101401
ns3.feg.de (142.132.212.110)2026101401
ns3.feg.de (2a01:4f8:262:50cf::2222:53)2026101401
ns4.feg.de (109.230.236.195)2026101401
ns4.feg.de (2a05:bec0:1:3::53)2026101401

Checks

  • ✓ Serial 2026101401 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 1000h, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.feg.de is one of the listed nameservers.
  • ✓ Contact support@feg.de #25
    The SOA RNAME support.feg.de means support@feg.de.
  • ✓ Date-based serial #26
    The serial 2026101401 follows the YYYYMMDDnn convention (2026-10-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

9 records at the apex

Found

Read from
88.198.217.62:53
TypeValueTTL
SOAns1.feg.de. support.feg.de. 2026101401 86400 7200 3600000 600600
NSns2.feg.de.86400
NSns3.feg.de.86400
NSns4.feg.de.86400
NSns1.feg.de.86400
A88.198.217.60600
MX10 mail.feg.de.86400
TXT"v=spf1 include:_spf.feg.de ~all"86400
TXT"google-site-verification=1b7827JAVUp_Yqx_2GPbRBpzPLSA49Zkp4TXMiNkz70"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 1d, NS 1d.
  • ✓ 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