SurfaceMap › r › rs2i.fr

rs2i.fr

Checked 2026-10-22 05:04 UTC · first added 2026-10-21
✗Problems found Score 49 of 100

Domain & DNS

fail

21 passed 4 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Open recursion
    Nameservers · These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: ns1.rs2i.fr (185.159.97.101), ns3.rs2i.fr (185.159.97.101). Disable recursion on authoritative servers.
    #16
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.rs2i.fr (185.159.97.101): 145 records; ns3.rs2i.fr (185.159.97.101): 145 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 185.159.97.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.rs2i.fr: "9.9.4-RedHat-9.9.4-74.el7_6.1"; ns2.rs2i.fr: "9.9.5-9+deb8u6-Debian"; ns3.rs2i.fr: "9.9.4-RedHat-9.9.4-74.el7_6.1". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · 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

Recent checks

✗

Full report

Domain & DNS report for rs2i.fr ›

Mail

fail

23 passed 3 warn 1 failed

Areas

✓SPF ✗DMARC ✓DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for rs2i.fr ›