neeltjejans.nl

Checked 22 October 2026, 14:41 UTC · via 8.8.8.8
✗Problems found
19 passed 6 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 ip4:195.77.203.170 ptr:madaoex03.aspro-ocio.es include:spf.protection.outlook.com include:recreatex.be include:spf.syscon.nl mx ~all
DNS lookups
6 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
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 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

fail

p=none (_dmarc.neeltjejans.nl)

Found

Record
v=DMARC1; p=none; sp=none; pct=100
Found at
_dmarc.neeltjejans.nl
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to

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: selector1

Found

Selectors
selector1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits

Checks

  • ✓ Keys found: selector1 #7
    DKIM keys found for this domain with selectors: selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits.
  • ✓ 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

3 mail servers

Found

PriorityHostRecordsReverse DNS
0neeltjejans-nl.mail.protection.outlook.comA 52.101.73.126 A 52.101.68.10 A 52.101.68.21 A 52.101.181.156 AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:c967::c AAAA 2a01:111:f403:ca04::email-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-wa4pr05cu00104.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-cpjpr05cu00204.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.inbound.protection.outlook.com ✓
50mail.zeelandnet.nlA 62.45.70.150mail.zeelandnet.nl ✓
100mail.aspro-ocio.esA 195.77.203.172no PTR

Checks

  • ✓ 3 MX records #9
    Found 3 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: mail.zeelandnet.nl, mail.aspro-ocio.es
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 195.77.203.172 (mail.aspro-ocio.es). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
neeltjejans-nl.mail.protection.outlook.comnone-
mail.zeelandnet.nlnone-
mail.aspro-ocio.esnone-

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