lovers.nl

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

SPF

fail

SPF record published

Found

Record
v=spf1 a mx ptr ptr:mail.lovers.nl ip4:89.184.172.0/24 include:eu.mailgun.org include:spf.protection.outlook.com include:25153734.spf05.hubspotemail.net include:email.freshdesk.com ~all
DNS lookups
15 of 10
Void lookups
0 of 2

Checks

  • !
    Uses deprecated ptr mechanism
    The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • ✗
    15 DNS lookups, over the limit of 10
    SPF record needs 15 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #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.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.lovers.nl)

Found

Record
v=DMARC1; p=none;
Found at
_dmarc.lovers.nl
TagValueMeaning
vDMARC1Version
pnonePolicy

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

pass

Selectors: k1

Found

Selectors
k1
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 2048 bits

Checks

  • ✓ Keys found: k1 #7
    DKIM keys found for this domain with selectors: k1
  • ✓ Strong keys #23
    DKIM keys are strong enough: k1: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
34505, 2371
Signatures valid until
6 December 2026, 14:25 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-12-06 #21
    DNSKEY signatures are valid until 2026-12-06T14:25:23Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
0lovers-nl.mail.protection.outlook.comA 52.101.68.15 A 52.101.73.145 A 52.101.91.21 A 52.101.73.126 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca04::e AAAA 2a01:111:f403:ca21::c AAAA 2a01:111:f403:ca3c::amail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓
10filter01.mx-relay.comA 38.101.250.150fe3-r2-in.atl06.l.antispamcloud.com ✓
20filter02.mx-relay.comA 38.101.250.150fe3-r2-in.atl06.l.antispamcloud.com ✓
30fallbackdt.mx-relay.comA 38.101.250.150fe3-r2-in.atl06.l.antispamcloud.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: filter01.mx-relay.com, filter02.mx-relay.com, fallbackdt.mx-relay.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 11 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
lovers-nl.mail.protection.outlook.comnone-
filter01.mx-relay.comnone-
filter02.mx-relay.comnone-
fallbackdt.mx-relay.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