mega.be

Checked 22 October 2026, 06:50 UTC · via 8.8.8.8
!Passed with warnings
27 passed 1 warning 0 failed 5 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

info

dns10.ovh.net, ns10.ovh.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns10.ovh.net, ns10.ovh.net
NS in the zone
dns10.ovh.net, ns10.ovh.net
NameserverAddressesNetwork (AS)Glue
dns10.ovh.net5.135.85.109 2001:41d0:d00:6100::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns10.ovh.net5.39.20.253 2001:41d0:b00:3a00::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns10.ovh.net, ns10.ovh.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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 4 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns10.ovh.net 5.135.85.109NOERROR, 16 ms, authoritativenoyes / yesrefused-
dns10.ovh.net 2001:41d0:d00:6100::2NOERROR, 21 ms, authoritativenoyes / yesrefused-
ns10.ovh.net 5.39.20.253NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns10.ovh.net 2001:41d0:b00:3a00::2NOERROR, 15 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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 2092506448 · primary dns10.ovh.net

Found

Primary (MNAME)
dns10.ovh.net
Contact (RNAME)
tech.ovh.net
Serial
2092506448
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
dns10.ovh.net (5.135.85.109)2092506448
dns10.ovh.net (2001:41d0:d00:6100::2)2092506448
ns10.ovh.net (5.39.20.253)2092506448
ns10.ovh.net (2001:41d0:b00:3a00::2)2092506448

Checks

  • ✓ Serial 2092506448 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 1000h, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns10.ovh.net is one of the listed nameservers.
  • ✓ Contact tech@ovh.net #25
    The SOA RNAME tech.ovh.net means tech@ovh.net.
  • ✓ Timestamp serial #26
    The serial 2092506448 is a Unix timestamp (2036-04-22 19:47 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
19 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
42812RSASHA256 (8)SHA256 45E52CF863969D3E…yes

DNSKEY in the zone

Key tagRoleAlgorithm
42812KSK (257)RSASHA256 (8)
47061ZSK (256)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 42812 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-19 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-19 13:27 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

28 records at the apex

Found

Read from
5.135.85.109:53
TypeValueTTL
SOAdns10.ovh.net. tech.ovh.net. 2092506448 86400 3600 3600000 30060
NSdns10.ovh.net.60
NSns10.ovh.net.60
A212.166.22.8260
MX0 mega-be.mail.protection.outlook.com.180
TXT"_globalsign-domain-verification=h7yGXPViU7HUpaZyt6V-Mr26643obimR2XMnq6yO9h"60
TXT"v=spf1 include:spf.protection.outlook.com include:_spf.atlassian.net include:spf.mandrillapp.com include:mx.ovh.com -all"60
TXT"google-site-verification=wUG0LRgBy0RuC698chSGfJYgoX-QliSKFSV7CwulNtA"60
TXT"jetbrains-domain-verification=8vzyd9px13vod3t1edw3mfwon"60
TXT"MS=ms44636397"60
TXT"W46QiQuSc9Zd2k5WZz75yBeVjvHdi1VE"60
TXT"facebook-domain-verification=d5rai5d56muxkyrv5rts9zxsojn7di"60
TXT"google-site-verification=8cuP9UkxLJkSMUp5dwDK-zYHRm9mRyPz6uHooj-ADf4"60
TXT"anthropic-domain-verification-2fg9v4=Q3JgYPwQRUMpYCUq7poFdAGXB"60
TXT"google-site-verification=3oO2-TssCstdEaJRByusXLN7Yw7niiY6D3HJwPTvmYU"60
TXT"twilio-domain-verification=a786e66270c51021ecfcea03f0a24eca"60
TXT"have-i-been-pwned-verification=dweb_npe3oz4z2wtgrqgvl75wmayb"60
TXT"google-site-verification=Ny9tr6vN_91vqFmuiOs7qjtpaYOZevEQAhSGMzpO5T0"60
TXT"atlassian-domain-verification=IiNQdLs38fil16C8kRVeBcaEXGCirSDTIgmlUpcGaBgDZUiiW2odGqiAZ5XJ54fl"60
TXT"DomainVerification=IL5PTNJF9TY3B22TMG2P1VVJRY5OO369HC33VVGD7OI8E0LLZSTD4AQI3NRIZ5JZ"60
TXT"_globalsign-domain-verification=4n3Ch0YWlaKmNt5hMZdu9nPGT6AVp-5gQjJQYzeLow"60
TXT"atlassian-domain-verification=h42CFNGcIRkkywaZIkngGVXxxfEF0nPaptEqKz0RC1muvB/1uwRx7DkQZmUO/JQY"60
TXT"atlassian-sending-domain-verification=d4741085-4e71-4802-b638-a29bf7338424"60
TXT"_globalsign-domain-verification=Kl0K5It_46-ysL_QB6pkQ_bg65UmyX54kmiOT4aW4z"60
TXT"_globalsign-domain-verification=_HkbdMWURr9LKVevJ98S3FX1V3r7aZGgEttWWt0xpF"60
CAA0 issue "letsencrypt.org"60
CAA0 issuewild "sectigo.com"60
CAA0 issue "sectigo.com"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (3m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, sectigo.com.