SurfaceMap › c › cleiss.fr

cleiss.fr

Checked 2026-10-22 02:20 UTC · first added 2026-10-21
✗Problems found Score 54 of 100

Domain & DNS

warn

21 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers iSOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.celeste.fr (glue 83.142.144.247, zone 83.142.144.247, 2001:ab8:100:2::); ns3.celeste.fr (glue 83.142.144.248, zone 83.142.144.248, 2001:ab8:100:3::). 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: ns1.celeste.fr: "9.11.5-P4-5.1+deb10u2-Debian"; ns2.celeste.fr: "9.11.5-P4-5.1+deb10u2-Debian"; ns3.celeste.fr: "9.11.5-P4-5.1+deb10u2-Debian". 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 cleiss.fr ›

Mail

fail

14 passed 9 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
  • !
    3 of 10 DNS lookups, with problems
    SPF · SPF record needs 3 DNS lookups (limit is 10). Problems found: include:spf.ecritel.net does not exist or has no records.
    #2
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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: mx-mibc-fr-01.mailinblack.com
    #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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 40.89.148.181 (mx-mibc-fr-01.mailinblack.com). Ask your hosting provider to set one.
    #30
  • !
    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 cleiss.fr ›