tele2.nl

SPF record published

Found

Record

v=spf1 include:mailplus.nl include:_spf_mx.solvinity.com include:spf.flowmailer.net include:spf1.tripolis.com include:spf2.tripolis.com include:spf.slgnt.eu ip4:212.247.154.0/23 ip4:212.247.156.0/27 ip4:94.103.21.49 ip4:94.103.21.65 ip4:193.12.60.45 ip4:193.12.60.46 ip4:193.12.60.47 ip4:193.12.60.48 ip4:62.58.50.0/24 ip4:82.215.18.0/28 ip4:82.215.18.96/28 ip4:217.149.218.0/24 ip4:62.58.48.0/24 ip4:188.190.114.141 ip4:188.190.114.142 ~all

DNS lookups

9 of 10

Void lookups

2 of 2

Problem

include:spf1.tripolis.com does not exist or has no records

Problem

include:spf2.tripolis.com does not exist or has no records

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• !

  9 of 10 DNS lookups, with problems

  SPF record needs 9 DNS lookups (limit is 10). Problems found: include:spf1.tripolis.com does not exist or has no records; include:spf2.tripolis.com 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.
• !

  2 void lookups

  2 include/redirect targets does not exist or has no records (limit is 2). This usually is a stale include; remove it.

  #26
• ✓ No overly broad IP ranges #27

  All ip4/ip6 ranges are narrow enough.

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

2 mail servers

Found

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: mx10.se.isp-net.nl, mx20.se.isp-net.nl

  #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 does not match

  The PTR name of these addresses does not resolve back to the same address: 38.111.198.185 -> fe2-r2-in.la10.l.antispamcloud.com, 38.111.198.185 -> fe2-r2-in.la10.l.antispamcloud.com.

  #30

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

Found

DANE (TLSA records)

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