orange.be

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

ns3.orange.be, ns4.orange.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns3.orange.be, ns4.orange.be
NS in the zone
ns3.orange.be, ns4.orange.be
NameserverAddressesNetwork (AS)Glue
ns3.orange.be212.224.255.253AS47377 Orange_Belgium_SA - Orange Belgium SA, BE212.224.255.253
ns4.orange.be212.224.249.253AS47377 Orange_Belgium_SA - Orange Belgium SA, BE212.224.249.253

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.orange.be, ns4.orange.be.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns3.orange.be, ns4.orange.be.
  • ✓ 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 (AS47377 (Orange_Belgium_SA - Orange Belgium SA, BE): 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 .be
    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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.orange.be 212.224.255.253NOERROR, 22 ms, authoritativenoyes / yesrefused-
ns4.orange.be 212.224.249.253NOERROR, 23 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.
  • ✓ 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 2025081732 · primary ns3.orange.be

Found

Primary (MNAME)
ns3.orange.be
Contact (RNAME)
dnsmaster.orange.be
Serial
2025081732
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns3.orange.be (212.224.255.253)2025081732
ns4.orange.be (212.224.249.253)2025081732

Checks

  • ✓ Serial 2025081732 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.orange.be is one of the listed nameservers.
  • ✓ Contact dnsmaster@orange.be #25
    The SOA RNAME dnsmaster.orange.be means dnsmaster@orange.be.
  • ✓ Date-based serial #26
    The serial 2025081732 follows the YYYYMMDDnn convention (2025-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

warn

14 records at the apex

Found

Read from
212.224.255.253:53
TypeValueTTL
SOAns3.orange.be. dnsmaster.orange.be. 2025081732 10800 3600 1209600 90028800
NSns3.orange.be.300
NSns4.orange.be.300
A45.60.100.222300
A107.154.79.222300
MX5 mxas1.orange.be.120
MX10 mxas2.orange.be.120
TXT"globalsign-domain-verification=DDD2B05077975BE007DC02950790858D"86400
TXT"globalsign-domain-verification=22B7EA0BC947CAF38D2BB9BEFDA19D57"86400
TXT"_rywt6qxci0dul78reoz4jyqrpm4a22r"86400
TXT"_nuck3lt67kw53713ku2dfdftnrg1fct"86400
TXT"v=spf1 include:_spf1.orange.be include:_spf2.orange.be include:_spf3.orange.be include:sendgrid.net a:mails.cellfleetmanager.com include:_spf.salesforce.com -all"86400
TXT"qmp7u73on0qsm0pi9uu1dd5422"86400
TXT"globalsign-domain-verification=A9C5647441AA3A99A4503184D99ED539"86400

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 5m; 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.
  • 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