humphreys.nl

Checked 22 October 2026, 13:51 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a ip4:5.200.15.114 ip6:2a00:1630:12a::e include:spf.antispamcloud.com include:spf.afas.online include:spf.spamservice.nl ip4:109.237.218.248 include:spf.pepperfield.eu ip4:5.61.250.232 ip4:185.10.158.42 ip4:136.144.217.131 ip6:2a01:7c8:d003:4de:5054:ff:fea2:7c19 -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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=reject (_dmarc.humphreys.nl)

Found

Record
v=DMARC1; p=reject; rua=mailto:dmarc-reports@fpcore.nl
Found at
_dmarc.humphreys.nl
External report address
mailto:dmarc-reports@fpcore.nl (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc-reports@fpcore.nlAggregate report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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-reports@fpcore.nl
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@fpcore.nl (needs humphreys.nl._report._dmarc.fpcore.nl). Ask the report provider to publish the record, or check the address.
    #29

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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
51155
Signatures valid until
5 November 2026, 00:00 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-11-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

pass

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.spamdefence.nlA 154.59.193.124 AAAA 2001:978:2:6::f:124fe3-r3-in.du01.l.antispamcloud.com ✓ fe3-r3-in.du01.l.antispamcloud.com ✓
20mx2.spamdefence.nlA 149.13.75.27 AAAA 2001:978:2:7::162:100fe1-r3-in.fra02.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓
30mx3.spamdefence.nlA 154.59.104.23 AAAA 2001:978:2:2c::137:100fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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.
  • ✓ 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.
  • ✓ Reverse DNS confirmed #30
    All 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.spamdefence.nlnone-
mx2.spamdefence.nlnone-
mx3.spamdefence.nlnone-

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