ville-montbrison.fr

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: hh101.e-liance.net. hh101.e-liance.net, ns1auth.e-liance.net, ns2auth.e-liance.net report NS hh101.e-liance.net ns1auth.e-liance.net ns2auth.e-liance.net.

SOA · The nameservers serve different versions of the zone: 2026100601 on hh101.e-liance.net (93.95.232.35), ns2auth.e-liance.net (213.56.79.170), ns2auth.e-liance.net (2a01:c910:8022:bb00::a); 2026102201 on ns1auth.e-liance.net (195.189.64.10), ns1auth.e-liance.net (2a00:c000:1::a). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

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.

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

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits). Rotate to a 2048-bit key.

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:informatique_dmarc@loireforez.fr (needs ville-montbrison.fr._report._dmarc.loireforez.fr). Ask the report provider to publish the record, or check the address.

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.