SurfaceMap › c › canon.fr

canon.fr

Checked 2026-10-22 02:05 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

23 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-206.akam.net: "41824.7"; a1-206.akam.net: "41824.11"; a11-65.akam.net: "41824.10"; a11-65.akam.net: "41824.5"; a14-66.akam.net: "48878.26"; a14-66.akam.net: "48878.27"; a18-67.akam.net: "48878.29"; a18-67.akam.net: "48878.31"; a26-64.akam.net: "48878.31"; a26-64.akam.net: "48878.26"; a9-65.akam.net: "41824.8"; a9-65.akam.net: "41824.6". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 15m.
    #23
  • !
    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 canon.fr ›

Mail

warn

21 passed 5 warn 0 failed

Areas

iSPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    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 canon.fr ›