resto.be

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

ns.resto.be, ns2.resto.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.resto.be, ns2.resto.be
NS in the zone
ns.resto.be, ns2.resto.be
NameserverAddressesNetwork (AS)Glue
ns.resto.be212.3.255.25AS3356 LEVEL3 - Level 3 Parent, LLC, US212.3.255.25
ns2.resto.be212.3.255.78AS3356 LEVEL3 - Level 3 Parent, LLC, US212.3.255.78

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.resto.be, ns2.resto.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: ns.resto.be, ns2.resto.be.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 212.3.255.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS3356 (LEVEL3 - Level 3 Parent, LLC, 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 .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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.resto.be 212.3.255.25NOERROR, 19 ms, authoritativenoyes / yesrefusedMicrosoft DNS 6.1.7601 (1DB15F75)
ns2.resto.be 212.3.255.78NOERROR, 18 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: ns.resto.be: "Microsoft DNS 6.1.7601 (1DB15F75)". 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 2003122118 · primary ns.resto.be

Found

Primary (MNAME)
ns.resto.be
Contact (RNAME)
hostmaster.resto.be
Serial
2003122118
Refresh / retry
86400 s / 14400 s
Expire
604800 s
Negative TTL
5 s

Serial per nameserver

NameserverSerial
ns.resto.be (212.3.255.25)2003122118
ns2.resto.be (212.3.255.78)2003122118

Checks

  • ✓ Serial 2003122118 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 5s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 4h, expire 7d, negative TTL 5s.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.resto.be is one of the listed nameservers.
  • ✓ Contact hostmaster@resto.be #25
    The SOA RNAME hostmaster.resto.be means hostmaster@resto.be.
  • ✓ Date-based serial #26
    The serial 2003122118 follows the YYYYMMDDnn convention (2003-12-21).

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

11 records at the apex

Found

Read from
212.3.255.25:53
TypeValueTTL
SOAns.resto.be. hostmaster.resto.be. 2003122118 86400 14400 604800 55
NSns2.resto.be.5
NSns.resto.be.5
A212.3.255.545
MX0 resto-be.mail.protection.outlook.com.5
TXT"v=DKIM1; k=rsa;" "p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCsxbHkvUvP/B4G4hQGD8p6Y7/vLaFnMa/8UQ9erzB1nUF43tKavfPXO7Z/0UP87stPzPY9BBEgDyC72gAPzfnkz163VCDLA4iCcrgOEr+Ec5FS0KYq4T1Ubausl+evYSRIpoXR0l0XK2Z5AychKPat7Rw2H+Gh5qcNJyOLROZw+wIDAQAB"5
TXT"google-site-verification=LXLc8diPmxWIexQ5F94NVTb-vm2KL43eUSU7MGZDgqQ"5
TXT"MS=ms36470300"5
TXT"v=spf1 include:_spf.salesforce.com include:spf.protection.outlook.com include:mail.zendesk.com ~all"5
TXT"facebook-domain-verification=ug7ep0kde7m7c6t9fzjif00gbwj9vw"5
TXT"brevo-code:39302155a36349dc660013d015cf0247"5

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (5s), MX (5s), NS (5s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 5s; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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