resto.fr

Checked 22 October 2026, 05:01 UTC · via 8.8.8.8
!Passed with warnings
20 passed 5 warnings 0 failed 6 info

Registration

info

.fr country-code · RESTO · expires 2027-07-01

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
RESTO
Registered
11 February 1999
Last changed
31 August 2026
Expires
1 July 2027
Status
active
Registry nameservers
ns.resto.be, ns2.resto.be
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr 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
    .fr is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-07-01 #3
    The registration is valid until 2027-07-01 (252 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns.resto.be, ns2.resto.be

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.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, US-
ns2.resto.be212.3.255.78AS3356 LEVEL3 - Level 3 Parent, LLC, US-

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.
  • ✓ 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 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, 20 ms, authoritativenoyes / yesrefusedMicrosoft DNS 6.1.7601 (1DB15F75)
ns2.resto.be 212.3.255.78NOERROR, 19 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

pass

serial 2004101332 · primary ns.resto.be

Found

Primary (MNAME)
ns.resto.be
Contact (RNAME)
hostmaster.resto.be
Serial
2004101332
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

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

Checks

  • ✓ Serial 2004101332 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1h.
  • ✓ 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 2004101332 follows the YYYYMMDDnn convention (2004-10-13).

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

9 records at the apex

Found

Read from
212.3.255.25:53
TypeValueTTL
SOAns.resto.be. hostmaster.resto.be. 2004101332 28800 7200 604800 360060
NSns.resto.be.7200
NSns2.resto.be.7200
A13.225.233.12960
MX0 resto-fr.mail.protection.outlook.com.3600
TXT"MS=ms70796781"3600
TXT"v=spf1 include:spf.protection.outlook.com -all"3600
TXT"google-site-verification=sjgL8Xfeng2k2YLQwYLZ002Bz1A-sV87dcpeh2ME-WE"3600
TXT"v=spf1 mx include:_spf.salesforce.com ~all"3600

Checks

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