bilder-space.de

Checked 21 October 2026, 21:40 UTC · via 8.8.8.8
!Passed with warnings
18 passed 3 warnings 0 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

ns1.ns-sv.net, ns2.ns-sv.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ns-sv.net, ns2.ns-sv.net
NS in the zone
ns1.ns-sv.net, ns2.ns-sv.net
NameserverAddressesNetwork (AS)Glue
ns1.ns-sv.net89.107.71.54AS30962 COMTRANCE-AS - comtrance service GmbH, DE-
ns2.ns-sv.net89.107.70.141AS30962 COMTRANCE-AS - comtrance service GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ns-sv.net, ns2.ns-sv.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS30962 (COMTRANCE-AS - comtrance service GmbH, DE): 2 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 .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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ns-sv.net 89.107.71.54NOERROR, 9 ms, authoritativenoyes / norefusedServed by PowerDNS - http://www.powerdns.com
ns2.ns-sv.net 89.107.70.141NOERROR, 8 ms, authoritativenoyes / norefusedServed by PowerDNS - http://www.powerdns.com

Checks

  • ✓ All respond #14
    All 2 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.ns-sv.net: "Served by PowerDNS - http://www.powerdns.com"; ns2.ns-sv.net: "Served by PowerDNS - http://www.powerdns.com".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.ns-sv.net (89.107.71.54), ns2.ns-sv.net (89.107.70.141).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2022091036 · primary ns1.ns-sv.net

Found

Primary (MNAME)
ns1.ns-sv.net
Contact (RNAME)
hostmaster.servado.de
Serial
2022091036
Refresh / retry
28800 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.ns-sv.net (89.107.71.54)2022091036
ns2.ns-sv.net (89.107.70.141)2022091036

Checks

  • ✓ Serial 2022091036 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 1h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ns-sv.net is one of the listed nameservers.
  • ✓ Contact hostmaster@servado.de #25
    The SOA RNAME hostmaster.servado.de means hostmaster@servado.de.
  • ✓ Date-based serial #26
    The serial 2022091036 follows the YYYYMMDDnn convention (2022-09-10).

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

5 records at the apex

Found

Read from
89.107.71.54:53
TypeValueTTL
SOAns1.ns-sv.net. hostmaster.servado.de. 2022091036 28800 3600 604800 60086400
NSns2.ns-sv.net.86400
NSns1.ns-sv.net.86400
A185.243.11.81300
MX10 rw0b51.webhosting.systems.300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, 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