facom.fr

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: a18-67.akam.net, a5-64.akam.net, a6-65.akam.net, a9-67.akam.net. a1-218.akam.net, a18-67.akam.net, a5-64.akam.net, a6-65.akam.net, a8-66.akam.net, a9-67.akam.net report NS a1-218.akam.net a18-67.akam.net a5-64.akam.net a6-65.akam.net a8-66.akam.net a9-67.akam.net.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-218.akam.net: "41824.9"; a1-218.akam.net: "41824.4"; a18-67.akam.net: "48878.31"; a18-67.akam.net: "48878.27"; a5-64.akam.net: "41824.10"; a5-64.akam.net: "41824.4"; a6-65.akam.net: "48878.30"; a8-66.akam.net: "48878.30"; a9-67.akam.net: "41824.10"; a9-67.akam.net: "41824.11". Hide or replace the version string.

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.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-00254701.gslb.pphosted.com, mxb-00254701.gslb.pphosted.com, reply.s50.exacttarget.com

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.