metrogroup.de

Checked 21 October 2026, 23:22 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.f5cloudservices.com, ns2.f5cloudservices.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.f5cloudservices.com, ns2.f5cloudservices.com
NS in the zone
ns1.f5clouddns.com, ns1.f5cloudservices.com, ns2.f5clouddns.com, ns2.f5cloudservices.com
NameserverAddressesNetwork (AS)Glue
ns1.f5clouddns.com (zone only)107.162.234.197 2604:e180:1071::3:1AS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-
ns1.f5cloudservices.com107.162.234.197 2604:e180:1071::3:1AS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-
ns2.f5clouddns.com (zone only)107.162.176.221 2604:e180:1071::ffff:6ba2:b0ddAS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-
ns2.f5cloudservices.com107.162.176.221 2604:e180:1071::ffff:6ba2:b0ddAS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.f5cloudservices.com, ns2.f5cloudservices.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.f5clouddns.com, ns2.f5clouddns.com. ns1.f5clouddns.com, ns1.f5cloudservices.com, ns2.f5clouddns.com, ns2.f5cloudservices.com report NS ns1.f5clouddns.com ns1.f5cloudservices.com ns2.f5clouddns.com ns2.f5cloudservices.com.
    #7
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2604:e180:1071::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS55002 (DEFENSE-NET - F5, Inc., US): 8 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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.f5clouddns.com 107.162.234.197NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns1.f5clouddns.com 2604:e180:1071::3:1NOERROR, 174 ms, authoritativenoyes / yesrefused-
ns1.f5cloudservices.com 107.162.234.197NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns1.f5cloudservices.com 2604:e180:1071::3:1NOERROR, 169 ms, authoritativenoyes / yesrefused-
ns2.f5clouddns.com 107.162.176.221NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns2.f5clouddns.com 2604:e180:1071::ffff:6ba2:b0ddNOERROR, 28 ms, authoritativenoyes / yesrefused-
ns2.f5cloudservices.com 107.162.176.221NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.f5cloudservices.com 2604:e180:1071::ffff:6ba2:b0ddNOERROR, 30 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

warn

serial 2009093446 · primary ns.mgi.de

Found

Primary (MNAME)
ns.mgi.de
Contact (RNAME)
hostmaster.mgi.de
Serial
2009093446
Refresh / retry
600 s / 300 s
Expire
2419200 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.f5clouddns.com (107.162.234.197)2009093446
ns1.f5clouddns.com (2604:e180:1071::3:1)2009093446
ns1.f5cloudservices.com (107.162.234.197)2009093446
ns1.f5cloudservices.com (2604:e180:1071::3:1)2009093446
ns2.f5clouddns.com (107.162.176.221)2009093446
ns2.f5clouddns.com (2604:e180:1071::ffff:6ba2:b0dd)2009093446
ns2.f5cloudservices.com (107.162.176.221)2009093446
ns2.f5cloudservices.com (2604:e180:1071::ffff:6ba2:b0dd)2009093446

Checks

  • ✓ Serial 2009093446 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 10m is outside 20m–1d. Current values: refresh 10m, retry 5m, expire 28d, negative TTL 15m.
    #23
  • i
    Hidden master
    The primary nameserver ns.mgi.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@mgi.de #25
    The SOA RNAME hostmaster.mgi.de means hostmaster@mgi.de.
  • ✓ Timestamp serial #26
    The serial 2009093446 is a Unix timestamp (2033-08-31 09:30 UTC).

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

8 records at the apex

Found

Read from
107.162.234.197:53
TypeValueTTL
SOAns.mgi.de. hostmaster.mgi.de. 2009093446 600 300 2419200 9003600
NSns2.f5cloudservices.com.3600
NSns1.f5cloudservices.com.3600
NSns2.f5clouddns.com.3600
NSns1.f5clouddns.com.3600
A4.175.117.2243600
TXT"acas.mnom.io=DNSint"3600
TXT"v=spf1 -all"3600

Checks

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