byak.de

Checked 21 October 2026, 22:04 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 5 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.m-online.net, ns2.m-online.net, ns3.m-online.net, ns4.m-online.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.m-online.net, ns2.m-online.net, ns3.m-online.net, ns4.m-online.net
NS in the zone
ns1.m-online.net, ns2.m-online.net, ns3.m-online.net, ns4.m-online.net
NameserverAddressesNetwork (AS)Glue
ns1.m-online.net212.18.0.8 2001:a60:0:11::53AS8767 MNET-AS - M-net Telekommunikations GmbH, DE AS8767 MNET-AS - M-net Telekommunikations GmbH, DE-
ns2.m-online.net212.18.3.8AS8767 MNET-AS - M-net Telekommunikations GmbH, DE-
ns3.m-online.net217.160.41.67 2001:8d8:1801:8039::1AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-
ns4.m-online.net212.114.171.64 2001:a60:0:20::53AS8767 MNET-AS - M-net Telekommunikations GmbH, DE AS8767 MNET-AS - M-net Telekommunikations GmbH, DE-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.m-online.net, ns2.m-online.net, ns3.m-online.net, ns4.m-online.net.
  • ✓ 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 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS8560 (IONOS-AS - IONOS SE, DE): 2 addresses; AS8767 (MNET-AS - M-net Telekommunikations GmbH, DE): 5 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns2.m-online.net.
    #13

Nameservers

pass

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.m-online.net 212.18.0.8NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns1.m-online.net 2001:a60:0:11::53NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.m-online.net 212.18.3.8NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns3.m-online.net 217.160.41.67NOERROR, 116 ms, authoritativenoyes / yesrefused-
ns3.m-online.net 2001:8d8:1801:8039::1NOERROR, 116 ms, authoritativenoyes / yesrefused-
ns4.m-online.net 212.114.171.64NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns4.m-online.net 2001:a60:0:20::53NOERROR, 6 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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

pass

serial 2026081700 · primary ns1.m-online.net

Found

Primary (MNAME)
ns1.m-online.net
Contact (RNAME)
hostmaster.m-net.de
Serial
2026081700
Refresh / retry
3600 s / 1800 s
Expire
3600000 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.m-online.net (212.18.0.8)2026081700
ns1.m-online.net (2001:a60:0:11::53)2026081700
ns2.m-online.net (212.18.3.8)2026081700
ns3.m-online.net (217.160.41.67)2026081700
ns3.m-online.net (2001:8d8:1801:8039::1)2026081700
ns4.m-online.net (212.114.171.64)2026081700
ns4.m-online.net (2001:a60:0:20::53)2026081700

Checks

  • ✓ Serial 2026081700 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 1000h, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.m-online.net is one of the listed nameservers.
  • ✓ Contact hostmaster@m-net.de #25
    The SOA RNAME hostmaster.m-net.de means hostmaster@m-net.de.
  • ✓ Date-based serial #26
    The serial 2026081700 follows the YYYYMMDDnn convention (2026-08-17).

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

11 records at the apex

Found

Read from
212.18.0.8:53
TypeValueTTL
SOAns1.m-online.net. hostmaster.m-net.de. 2026081700 3600 1800 3600000 600600
NSns2.m-online.net.600
NSns4.m-online.net.600
NSns3.m-online.net.600
NSns1.m-online.net.600
A78.47.98.182600
MX10 byak-de.mail.protection.outlook.com.3600
TXT"jhjwkf3vt35kck2y32xs96y95n9f3bpy"3600
TXT"MS=ms63879139"3600
TXT"201709181245310pydml7oxmopgr22lapjw9hzyufmnm1zr746h3apt6vjblufur"3600
TXT"v=spf1 a:mail.byak.de a:dedi4320.your-server.de ip4:212.114.247.239 ip4:78.47.98.182 ip4:136.243.166.247 include:spf.protection.outlook.com include:spf.w4ymail.at include:spf.sepa.at ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 1h, NS 10m. The NS TTL at the parent is 1d and in the zone 10m; 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