SurfaceMap › m › mgm.fr

mgm.fr

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

Domain & DNS

warn

19 passed 6 warn 0 failed

Areas

!Registration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Expires in 24 days
    Registration · The registration expires on 2026-11-15. Make sure it is renewed.
    #3
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dnsa01.univ-avignon.fr, dnsa02.univ-avignon.fr; only in the zone: dns.univ-avignon.fr, dns2.univ-avignon.fr. dns.univ-avignon.fr, dns2.univ-avignon.fr, dnsa01.univ-avignon.fr, dnsa02.univ-avignon.fr report NS dns.univ-avignon.fr dns2.univ-avignon.fr.
    #7
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 195.83.163.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    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: dns.univ-avignon.fr: "PowerDNS Authoritative Server 4.9.16"; dns2.univ-avignon.fr: "PowerDNS Authoritative Server 4.9.16"; dnsa01.univ-avignon.fr: "PowerDNS Authoritative Server 4.9.16"; dnsa02.univ-avignon.fr: "PowerDNS Authoritative Server 4.9.16". 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 mgm.fr ›

Mail

fail

19 passed 4 warn 2 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✗
    No DKIM keys published
    DKIM · _domainkey.mgm.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.relay.renater.fr, mx2.relay.renater.fr
    #11
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@univ-avignon.fr (needs mgm.fr._report._dmarc.univ-avignon.fr). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 mgm.fr ›