serem.fr

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.targetweb.io: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16"; dns2.targetweb.eu: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16"; dns3.targetweb.link: "9.11.36-RedHat-9.11.36-16.el8_10.16"; dns4.targetweb.xyz: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16". 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.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (5s), MX (1m). Low TTLs are useful just before a planned change.

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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

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 IP addresses: 31.204.81.154, 80.11.69.191

MX · The following MX hosts could not be resolved to IPv6 addresses: mail.serem.fr, 31.204.81.154, 80.11.69.191

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.