mess.be

Checked 22 October 2026, 06:50 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 warnings 0 failed 6 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

warn

ns5.private-nameserver.net, ns6.private-nameserver.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns5.private-nameserver.net, ns6.private-nameserver.net
NS in the zone
ns5.private-nameserver.net, ns6.private-nameserver.net
NameserverAddressesNetwork (AS)Glue
ns5.private-nameserver.net205.185.112.60AS53667 PONYNET - FranTech Solutions, US-
ns6.private-nameserver.net199.195.255.60AS53667 PONYNET - FranTech Solutions, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns5.private-nameserver.net, ns6.private-nameserver.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 (AS53667 (PONYNET - FranTech Solutions, US): 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
ns5.private-nameserver.net 205.185.112.60NOERROR, 139 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17
ns6.private-nameserver.net 199.195.255.60NOERROR, 83 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns5.private-nameserver.net: "PowerDNS Authoritative Server 4.9.17"; ns6.private-nameserver.net: "PowerDNS Authoritative Server 4.9.17". 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

warn

serial 2024092403 · primary ns5.private-nameserver.net

Found

Primary (MNAME)
ns5.private-nameserver.net
Contact (RNAME)
urgent.messmedia.be
Serial
2024092403
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns5.private-nameserver.net (205.185.112.60)2024092403
ns6.private-nameserver.net (199.195.255.60)2024092403

Checks

  • ✓ Serial 2024092403 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns5.private-nameserver.net is one of the listed nameservers.
  • ✓ Contact urgent@messmedia.be #25
    The SOA RNAME urgent.messmedia.be means urgent@messmedia.be.
  • ✓ Date-based serial #26
    The serial 2024092403 follows the YYYYMMDDnn convention (2024-09-24).

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
205.185.112.60:53
TypeValueTTL
SOAns5.private-nameserver.net. urgent.messmedia.be. 2024092403 3600 3600 1209600 864003600
NSns5.private-nameserver.net.3600
NSns6.private-nameserver.net.3600
A193.108.130.223600
MX20 mx3.mxfilter.net.3600
MX10 mx1.mxfilter.net.3600
MX10 mx2.mxfilter.net.3600
TXT"v=spf1 a mx ip4:193.108.130.22 include:spf.mxyeet.net ip6:2605:6400:3:fed5:1000:201:0:2 ~all"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