b-rail.be

Checked 22 October 2026, 06:04 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 0 failed 7 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.belgiantrain.be, ns2.belgiantrain.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.belgiantrain.be, ns2.belgiantrain.be
NS in the zone
ns1.belgiantrain.be, ns2.belgiantrain.be
NameserverAddressesNetwork (AS)Glue
ns1.belgiantrain.be185.180.44.4AS209704 nmbs-sncb - NV OR NATIONALE MAATSCHAPPIJ DER BELGISCHE SPOORWEGEN, BE185.180.44.4
ns2.belgiantrain.be185.180.45.4AS209704 nmbs-sncb - NV OR NATIONALE MAATSCHAPPIJ DER BELGISCHE SPOORWEGEN, BE185.180.45.4

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.belgiantrain.be, ns2.belgiantrain.be.
    #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 (AS209704 (nmbs-sncb - NV OR NATIONALE MAATSCHAPPIJ DER BELGISCHE SPOORWEGEN, 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
ns1.belgiantrain.be 185.180.44.4NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.belgiantrain.be 185.180.45.4NOERROR, 12 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

info

serial 312 · primary tapdnsp07.belgianrail.be

Found

Primary (MNAME)
tapdnsp07.belgianrail.be
Contact (RNAME)
please_set_email.absolutely.nowhere
Serial
312
Refresh / retry
10800 s / 3600 s
Expire
2419200 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.belgiantrain.be (185.180.44.4)312
ns2.belgiantrain.be (185.180.45.4)312

Checks

  • ✓ Serial 312 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 28d, negative TTL 15m.
  • i
    Hidden master (not resolvable)
    The primary nameserver tapdnsp07.belgianrail.be is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact please_set_email@absolutely.nowhere #25
    The SOA RNAME please_set_email.absolutely.nowhere means please_set_email@absolutely.nowhere.
  • ✓ Counter serial #26
    The serial 312 is a plain counter.

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
185.180.44.4:53
TypeValueTTL
SOAtapdnsp07.belgianrail.be. please_set_email.absolutely.nowhere. 312 10800 3600 2419200 90028800
NSns1.belgiantrain.be.28800
NSns2.belgiantrain.be.28800
MX10 brail-be0c.mail.protection.outlook.com.28800
TXT"KhQunum/uavhW7cPARthgG+IvkHB+ZoxiNJpCZu9ACIdmip6eWDm0hVUbO+VS/61AvsX7jADL/mZjhK//MRhrg=="28800
TXT"v=spf1 mx ip4:52.142.232.33 ip4:51.145.176.238 ip4:51.145.177.160 include:spf.protection.outlook.com ~all"28800
TXT"_co6v9jeqz89raqn9e6nypal2ihdxe0c"28800
TXT"_rhjylljltjb5f348lmcgk3c06zr0qbq"28800

Checks

  • ✓ TTLs within range #32
    TTLs: MX 8h, NS 8h. The NS TTL at the parent is 1d and in the zone 8h; 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