toshiba-tro.de

Checked 22 October 2026, 00:41 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.zonomi.com, ns6.zonomi.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.zonomi.com, ns6.zonomi.com
NS in the zone
ns1.zonomi.com, ns6.zonomi.com
NameserverAddressesNetwork (AS)Glue
ns1.zonomi.com45.79.211.52 2600:3c02::f03c:91ff:fe26:5defAS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns6.zonomi.com172.105.209.133 2400:8902::f03c:91ff:fe46:a4edAS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.zonomi.com, ns6.zonomi.com.
    #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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS63949 (AKAMAI-LINODE-AP - Akamai Connected Cloud, SG): 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 .com
    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
ns1.zonomi.com 45.79.211.52NOERROR, 108 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns1.zonomi.com 2600:3c02::f03c:91ff:fe26:5defNOERROR, 110 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns6.zonomi.com 172.105.209.133NOERROR, 258 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns6.zonomi.com 2400:8902::f03c:91ff:fe46:a4edNOERROR, 279 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1

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: ns1.zonomi.com: "PowerDNS Authoritative Server 4.4.1"; ns6.zonomi.com: "PowerDNS Authoritative Server 4.4.1". 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 43 · primary ns1.zonomi.com

Found

Primary (MNAME)
ns1.zonomi.com
Contact (RNAME)
soacontact.zonomi.com
Serial
43
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.zonomi.com (45.79.211.52)43
ns1.zonomi.com (2600:3c02::f03c:91ff:fe26:5def)43
ns6.zonomi.com (172.105.209.133)43
ns6.zonomi.com (2400:8902::f03c:91ff:fe46:a4ed)43

Checks

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

5 records at the apex

Found

Read from
45.79.211.52:53
TypeValueTTL
SOAns1.zonomi.com. soacontact.zonomi.com. 43 10800 3600 604800 360086400
NSns1.zonomi.com.3600
NSns6.zonomi.com.3600
A152.70.140.2413600
MX0 mail2.toshiba-tro.de.3600

Checks

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