miron.be

Checked 22 October 2026, 06:51 UTC · via 8.8.8.8
✗Problems found
22 passed 2 warnings 1 failed 4 info

Registration

info

.be country-code

Found

TLD
.be (country-code)
ICANN policies apply
no

Checks

  • i
    .be 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
    .be is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

pass

domain-for-sale.at, the-domains.website, visit.the-domains.website

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
domain-for-sale.at, the-domains.website, visit.the-domains.website
NS in the zone
domain-for-sale.at, the-domains.website, visit.the-domains.website
NameserverAddressesNetwork (AS)Glue
domain-for-sale.at18.193.37.16 2a05:d014:a67:a2a2::5001AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
the-domains.website142.93.233.228 2a03:b0c0:2:f0::78:1001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-
visit.the-domains.website77.68.16.186 2a00:da00:f22b:7400::1AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to domain-for-sale.at, the-domains.website, visit.the-domains.website.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .at, .website.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
domain-for-sale.at 18.193.37.16NOERROR, 4 ms, authoritativenoyes / norefused-
domain-for-sale.at 2a05:d014:a67:a2a2::5001NOERROR, 4 ms, authoritativenoyes / norefused-
the-domains.website 142.93.233.228NOERROR, 17 ms, authoritativenoyes / norefused-
the-domains.website 2a03:b0c0:2:f0::78:1001NOERROR, 15 ms, authoritativenoyes / norefused-
visit.the-domains.website 77.68.16.186NOERROR, 25 ms, authoritativenono / norefused-
visit.the-domains.website 2a00:da00:f22b:7400::1NOERROR, 20 ms, authoritativenoyes / norefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: visit.the-domains.website (77.68.16.186): read tcp 46.225.38.91:52938->77.68.16.186:53: read: connection reset by peer.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: domain-for-sale.at (18.193.37.16), domain-for-sale.at (2a05:d014:a67:a2a2::5001), the-domains.website (142.93.233.228), the-domains.website (2a03:b0c0:2:f0::78:1001), visit.the-domains.website (77.68.16.186), visit.the-domains.website (2a00:da00:f22b:7400::1).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2016080801 · primary domain-for-sale.at

Found

Primary (MNAME)
domain-for-sale.at
Contact (RNAME)
dns.domain-for-sale.at
Serial
2016080801
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
domain-for-sale.at (18.193.37.16)2016080801
domain-for-sale.at (2a05:d014:a67:a2a2::5001)2016080801
the-domains.website (142.93.233.228)2016080801
the-domains.website (2a03:b0c0:2:f0::78:1001)2016080801
visit.the-domains.website (77.68.16.186)2016080801
visit.the-domains.website (2a00:da00:f22b:7400::1)2016080801

Checks

  • ✓ Serial 2016080801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver domain-for-sale.at is one of the listed nameservers.
  • ✓ Contact dns@domain-for-sale.at #25
    The SOA RNAME dns.domain-for-sale.at means dns@domain-for-sale.at.
  • ✓ Date-based serial #26
    The serial 2016080801 follows the YYYYMMDDnn convention (2016-08-08).

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
18.193.37.16:53
TypeValueTTL
SOAdomain-for-sale.at. dns.domain-for-sale.at. 2016080801 14400 3600 604800 8640086400
NSdomain-for-sale.at.86400
NSthe-domains.website.86400
NSvisit.the-domains.website.86400
A75.2.126.6786400
TXT"v=spf1 -all"86400
TXT"2a6c68c32c4734b7ea8537a9cbc1437ec92a1ed6"86400
TXT"3b7c27e9f0a9a65475762775aabe83f7e0c01ed6"86400

Checks

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