afm-telethon.fr

Checked 22 October 2026, 01:27 UTC · via 8.8.8.8
!Passed with warnings
23 passed 6 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:103.224.174.158 ip4:103.224.174.159 ip4:103.224.174.160 ip4:103.224.174.161 ip4:103.224.174.162 ip4:103.224.174.163 ip4:202.22.174.26 ip4:202.22.174.254 ip4:202.22.171.132 ip4:202.22.171.133 ip4:46.235.17.249 ip4:46.235.17.250 ip4:46.235.17.251 ip4:167.89.60.75 ip4:153.92.250.87 ip4:54.229.96.1 ip4:54.229.96.23 ip4:54.229.96.27 ip4:54.229.96.36 ip4:54.229.96.53 ip4:54.229.96.66 ip4:193.50.67.62 ip4:207.253.198.2 ip4:89.185.41.126/31 ip4:89.185.41.128/29 ip4:89.185.41.55 ip4:89.185.41.4 ip4:89.185.41.83 ip4:89.185.41.5 ip4:89.185.41.20 ip4:89.185.41.244 ip4:89.185.41.143 ip4:89.185.41.233 ip4:89.185.41.208 ip4:89.185.41.106 ip4:89.185.41.174 ip4:194.51.172.0/24 ip4:80.74.77.110 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/24 ip4:223.165.120.0/24 ip4:148.59.136.57 include:_spf2.afm-telethon.fr include:spf.tipimail.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 9 of 10 DNS lookups #2
    SPF record needs 9 DNS lookups (limit is 10).
  • ✓ 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.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.afm-telethon.fr)

Found

Record
v=DMARC1; p=quarantine; sp=none; rua=mailto:dmarc@afm-telethon.fr; ruf=mailto:dmarc@afm-telethon.fr; rf=afrf; pct=100; ri=86400
Found at
_dmarc.afm-telethon.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@afm-telethon.frAggregate report addresses
rufmailto:dmarc@afm-telethon.frFailure report addresses
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@afm-telethon.fr
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, mta, s1, s2

Found

Selectors
mail, selector1, mta, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits
mtaRSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1, mta, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector1, mta, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), mta (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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

1 mail server

Found

PriorityHostRecordsReverse DNS
10afmtelethon-fr0i.mail.protection.outlook.comA 52.101.91.159 A 52.101.73.126 A 52.101.68.39 A 52.101.185.114 AAAA 2a01:111:f403:c967::8 AAAA 2a01:111:f403:ca09::24 AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca21::cmail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-db7pr03cu00607.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-cpjpr04cu00100.inbound.protection.outlook.com ✓ mail-am6pr02cu00204.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
afmtelethon-fr0i.mail.protection.outlook.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