snj.fr

Checked 22 October 2026, 05:15 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 7 info

Registration

info

.fr country-code · HAISOFT · expires 2027-08-04

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
HAISOFT
Registered
20 September 1999
Last changed
30 September 2026
Expires
4 August 2027
Status
active
Registry nameservers
dns2.haisoft.net, ds573.haisoft.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 2027-08-04 #3
    The registration is valid until 2027-08-04 (286 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

dns2.haisoft.net, ds573.haisoft.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
dns2.haisoft.net, ds573.haisoft.net
NS in the zone
dns2.haisoft.net, ds573.haisoft.net
NameserverAddressesNetwork (AS)Glue
dns2.haisoft.net91.212.26.200 2a0a:2f81:f:f::1AS16347 INHERENT - ADISTA SAS, FR AS16347 INHERENT - ADISTA SAS, FR-
ds573.haisoft.net91.212.26.73AS16347 INHERENT - ADISTA SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns2.haisoft.net, ds573.haisoft.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 91.212.26.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 (AS16347 (INHERENT - ADISTA SAS, FR): 3 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ds573.haisoft.net.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns2.haisoft.net 91.212.26.200NOERROR, 16 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-16.el8_10.6
dns2.haisoft.net 2a0a:2f81:f:f::1NOERROR, 16 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-16.el8_10.6
ds573.haisoft.net 91.212.26.73NOERROR, 17 ms, authoritativenoyes / yesrefusednone

Checks

  • ✓ All respond #14
    All 3 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: dns2.haisoft.net: "9.11.36-RedHat-9.11.36-16.el8_10.6". 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 2026091701 · primary ds573.haisoft.net

Found

Primary (MNAME)
ds573.haisoft.net
Contact (RNAME)
root.ds573.haisoft.net
Serial
2026091701
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
dns2.haisoft.net (91.212.26.200)2026091701
dns2.haisoft.net (2a0a:2f81:f:f::1)2026091701
ds573.haisoft.net (91.212.26.73)2026091701

Checks

  • ✓ Serial 2026091701 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ds573.haisoft.net is one of the listed nameservers.
  • ✓ Contact root@ds573.haisoft.net #25
    The SOA RNAME root.ds573.haisoft.net means root@ds573.haisoft.net.
  • ✓ Date-based serial #26
    The serial 2026091701 follows the YYYYMMDDnn convention (2026-09-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

7 records at the apex

Found

Read from
91.212.26.200:53
TypeValueTTL
SOAds573.haisoft.net. root.ds573.haisoft.net. 2026091701 10800 3600 604800 10800120
NSds573.haisoft.net.120
NSdns2.haisoft.net.120
A91.212.26.73120
MX10 ds573.haisoft.net.120
TXT"brevo-code:6fb47a5238dc4feb16b802c15058d35a"120
TXT"v=spf1 a mx a:mx10.relay.haisoft.net include:spf.haisoft.net -all"120

Checks

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