freitag.de

Checked 21 October 2026, 22:31 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

ns3.fcio.net, ns4.fcio.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns3.fcio.net, ns4.fcio.net
NS in the zone
ns3.fcio.net, ns4.fcio.net
NameserverAddressesNetwork (AS)Glue
ns3.fcio.net195.62.125.43 2a02:248:101:62::1423AS8648 ONE-NETWORK - dogado GmbH, DE AS8648 ONE-NETWORK - dogado GmbH, DE-
ns4.fcio.net185.105.255.54 2a06:3a80:0:2::43AS41981 FCIO - Flying Circus Internet Operations GmbH, DE AS41981 FCIO - Flying Circus Internet Operations GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.fcio.net, ns4.fcio.net.
    #6
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS41981 (FCIO - Flying Circus Internet Operations GmbH, DE): 2 addresses; AS8648 (ONE-NETWORK - dogado GmbH, DE): 2 addresses.
  • 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.fcio.net 195.62.125.43NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.6
ns3.fcio.net 2a02:248:101:62::1423NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.6
ns4.fcio.net 185.105.255.54NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.6
ns4.fcio.net 2a06:3a80:0:2::43NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.6

Checks

  • ✓ All respond #14
    All 4 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: ns3.fcio.net: "PowerDNS Authoritative Server 5.0.6"; ns4.fcio.net: "PowerDNS Authoritative Server 5.0.6". 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 2026091801 · primary ns3.fcio.net

Found

Primary (MNAME)
ns3.fcio.net
Contact (RNAME)
support.flyingcircus.io
Serial
2026091801
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns3.fcio.net (195.62.125.43)2026091801
ns3.fcio.net (2a02:248:101:62::1423)2026091801
ns4.fcio.net (185.105.255.54)2026091801
ns4.fcio.net (2a06:3a80:0:2::43)2026091801

Checks

  • ✓ Serial 2026091801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.fcio.net is one of the listed nameservers.
  • ✓ Contact support@flyingcircus.io #25
    The SOA RNAME support.flyingcircus.io means support@flyingcircus.io.
  • ✓ Date-based serial #26
    The serial 2026091801 follows the YYYYMMDDnn convention (2026-09-18).

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
195.62.125.43:53
TypeValueTTL
SOAns3.fcio.net. support.flyingcircus.io. 2026091801 10800 3600 1209600 180086400
NSns4.fcio.net.3600
NSns3.fcio.net.3600
A185.105.252.153600
AAAA2a02:248:101:62::12863600
MX0 freitag-de.mail.protection.outlook.com.3600
TXT"have-i-been-pwned-verification=af6355d3b6758d2ed22a53eee7ee603e"3600
TXT"google-site-verification=OMGZwKdw0SGQeHS-WIjhdLGWpFwcv0XXqsNIO5VVH_g"3600
TXT"google-site-verification=5s9jzZHvoCpxvOz18hZZg30y0V_syodfwyv7pARWSVA"3600
TXT"google-site-verification=0rj2YqmmTFnFHm4wvj3CEjeWd44sjWQOG0V5_Pj8Ia8"3600
TXT"v=spf1 ip4:213.61.61.171 include:spf.protection.outlook.com ~all"3600
TXT"google-site-verification=18FJF_TGC6jy2e9KULkTr9swgdCBq9YbgcMesPDJVjc"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, 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.
  • 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