SurfaceMap › o › optimize360.fr

optimize360.fr

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

Domain & DNS

fail

21 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.o2switch.net (109.234.160.5): dial tcp 109.234.160.5:53: i/o timeout; ns2.o2switch.net (109.234.161.5): dial tcp 109.234.161.5:53: i/o timeout.
    #19
  • !
    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.o2switch.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; ns2.o2switch.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)". 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 optimize360.fr ›

Mail

warn

22 passed 7 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    More than 5 MX records
    MX · Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    Applies to 90% of mail
    DMARC · DMARC policy only applies to 90% of failing mail (pct=90). Raise pct to 100 once you are confident in your setup.
    #18
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: email (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 optimize360.fr ›