ps.be

Checked 22 October 2026, 07:01 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 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

warn

ns1.myown.be, ns2.myown.eu

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.myown.be, ns2.myown.eu
NS in the zone
ns1.myown.be, ns2.myown.eu
NameserverAddressesNetwork (AS)Glue
ns1.myown.be20.56.43.12AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US20.56.43.12
ns2.myown.eu46.105.152.130AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.myown.be, ns2.myown.eu.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .be, .eu.
  • !
    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
ns1.myown.be 20.56.43.12NOERROR, 14 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
ns2.myown.eu 46.105.152.130NOERROR, 17 ms, authoritativenoyes / yesrefused-

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: ns1.myown.be: "9.18.39-0ubuntu0.22.04.7-Ubuntu". 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 1789494721 · primary ns1.myown.be

Found

Primary (MNAME)
ns1.myown.be
Contact (RNAME)
postmaster.myown.eu
Serial
1789494721
Refresh / retry
86400 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.myown.be (20.56.43.12)1789494721
ns2.myown.eu (46.105.152.130)1789494721

Checks

  • ✓ Serial 1789494721 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.myown.be is one of the listed nameservers.
  • ✓ Contact postmaster@myown.eu #25
    The SOA RNAME postmaster.myown.eu means postmaster@myown.eu.
  • ✓ Timestamp serial #26
    The serial 1789494721 is a Unix timestamp (2026-09-15 17:52 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

12 records at the apex

Found

Read from
20.56.43.12:53
TypeValueTTL
SOAns1.myown.be. postmaster.myown.eu. 1789494721 86400 3600 604800 36003600
NSns1.myown.be.3600
NSns2.myown.eu.3600
A37.59.85.353600
MX0 ps-be.mail.protection.outlook.com.3600
TXT"google-site-verification=YhwLFHm8T1jjm6EnMMqXFsIJNveEEx0Auqv0N6SAlQI"3600
TXT"Sendinblue-code:d9c0e59b77681fb3d4fd0e6a0455d763"3600
TXT"MS=ms99808689"3600
TXT"zoom = 10520450"3600
TXT"v=spf1 include:spf.flexmail.eu include:spf.mailjet.com include:spf.protection.outlook.com -all"3600
TXT"google-site-verification=tnawcUQwSfJmXm_It5Jjo5G-4TQVgWsA56mw2-QaNDw"3600
TXT"spf2.0/pra include:spf.flexmail.eu ?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