maisonslaffitte.fr

Checked 22 October 2026, 04:13 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 6 info

Registration

info

.fr country-code · INEXINE · expires 2026-12-23

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
INEXINE
Registered
9 May 2005
Last changed
31 January 2026
Expires
23 December 2026
Status
active
Registry nameservers
ns1.inexine.net, ns2.inexine.net
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 2026-12-23 #3
    The registration is valid until 2026-12-23 (62 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

ns1.inexine.net, ns2.inexine.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.inexine.net, ns2.inexine.net
NS in the zone
ns1.inexine.net, ns2.inexine.net
NameserverAddressesNetwork (AS)Glue
ns1.inexine.net46.105.230.65AS16276 OVH - OVH SAS, FR-
ns2.inexine.net46.105.230.66AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.inexine.net, ns2.inexine.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 one network
    all IPv4 addresses are in 46.105.230.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 (AS16276 (OVH - OVH SAS, FR): 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 .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
  • !
    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
ns1.inexine.net 46.105.230.65NOERROR, 16 ms, authoritativenoyes / yesrefused9.9.5-3ubuntu0.19-Ubuntu
ns2.inexine.net 46.105.230.66NOERROR, 16 ms, authoritativenoyes / yesrefused9.9.5-3-Ubuntu

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: ns1.inexine.net: "9.9.5-3ubuntu0.19-Ubuntu"; ns2.inexine.net: "9.9.5-3-Ubuntu". 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 2014102457 · primary ns1.inexine.net

Found

Primary (MNAME)
ns1.inexine.net
Contact (RNAME)
technique.inexine.com
Serial
2014102457
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.inexine.net (46.105.230.65)2014102457
ns2.inexine.net (46.105.230.66)2014102457

Checks

  • ✓ Serial 2014102457 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.inexine.net is one of the listed nameservers.
  • ✓ Contact technique@inexine.com #25
    The SOA RNAME technique.inexine.com means technique@inexine.com.
  • ✓ Date-based serial #26
    The serial 2014102457 follows the YYYYMMDDnn convention (2014-10-24).

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

13 records at the apex

Found

Read from
46.105.230.65:53
TypeValueTTL
SOAns1.inexine.net. technique.inexine.com. 2014102457 21600 3600 604800 600600
NSns1.inexine.net.600
NSns2.inexine.net.600
A54.37.182.50600
MX5 mx-mibc-fr-03.mailinblack.com.600
TXT"MS=ms56701417"600
TXT"_ju0v96ohzsq67ky6ma9gng1jrm7vei3"600
TXT"v=spf1 include:qd76zmpriw.powerspf.com ~all"600
TXT"apple-domain-verification=mcIteKhFbOEwZ4fG"600
TXT"globalsign-domain-verification=wovkxabuVaBbNMpMO2A3_zM-QeT7LNzR7IGMMDqV78"600
TXT"0LzhuiLFJYIDt8tme8lTcXt9Oz7Jq4wKGhQS7HAMhPUrb496zVMjYlYNms/Q0nH2O3Byjsd/FevLiY87vV+nFQ=="600
TXT"7gd9gm2twmf2gmgl48ffcbjcz3wbsws2"600
TXT"_2xhepwn7v571xj55sp57lxd5sgtr99k"600

Checks

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