lemagit.fr

Checked 22 October 2026, 03:49 UTC · via 8.8.8.8
✗Problems found
14 passed 4 warnings 3 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 include:zimbra.lemagit.fr include:mail.lemagit.fr include:mail2.lemagit.fr include:emagine.fr include:mktomail.com ~all
DNS lookups
12 of 10
Void lookups
3 of 2
Problem
include:zimbra.lemagit.fr does not exist or has no records
Problem
include:mail.lemagit.fr does not exist or has no records
Problem
include:mail2.lemagit.fr does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    12 DNS lookups, over the limit of 10
    SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:zimbra.lemagit.fr does not exist or has no records; include:mail.lemagit.fr does not exist or has no records; include:mail2.lemagit.fr does not exist or has no records.
    #2
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✗
    3 void lookups, over the limit of 2
    3 include/redirect targets do not exist or have no records. More than 2 makes receivers reject the SPF record (permerror). Remove the stale includes.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

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

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mxa-00051b01.gslb.pphosted.comA 148.163.141.45mx0b-00051b01.pphosted.com ✓
10mxb-00051b01.gslb.pphosted.comA 148.163.145.44mx0a-00051b01.pphosted.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mxa-00051b01.gslb.pphosted.com, mxb-00051b01.gslb.pphosted.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mxa-00051b01.gslb.pphosted.comnone-
mxb-00051b01.gslb.pphosted.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38