SurfaceMap › i › inrets.fr

inrets.fr

Checked 2026-10-22 03:30 UTC · first added 2026-10-21
✗Problems found Score 43 of 100

Domain & DNS

fail

22 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns0.inrets.fr (2001:660:3101:2::10): read udp [2a01:4f8:1c1c:eebf::1]:38529->[2001:660:3101:2::10]:53: i/o timeout.
    #14
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns0.inrets.fr (glue 137.121.254.33, zone 137.121.254.33, 2001:660:3101:2::10); ns1.inrets.fr (glue 137.121.250.16, zone 137.121.250.16, 2001:660:3101:2::11). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0.inrets.fr: "NSD 4.1.0"; ns1.inrets.fr: "NSD 4.1.0". 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 inrets.fr ›

Mail

fail

15 passed 6 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    Syntax errors
    SPF · Receivers reject the whole SPF record (permerror) because of: "ip4:137.121.250/24": not a valid IPv4 address or range.
    #25
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx2.lcpc.fr
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: s1. Remove t=y once DKIM works.
    #24
  • !
    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 inrets.fr ›