rocfriesepoort.nl

Checked 22 October 2026, 15:41 UTC · via 8.8.8.8
✗Problems found
17 passed 1 warning 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:213.136.12.226 ip4:149.210.191.75 ip4:149.210.191.54 ip4:62.209.53.50 ip4:34.249.196.78 ip4:34.251.157.56 ip4:34.252.27.239 ip4:35.157.154.159 ip4:35.157.187.101 ip4:89.41.169.208 ip6:2a01:7c8:aac7:348:5054:ff:fecf:63a8/64 include:spf.topdesk.net include:spf.afas.online include:sendgrid.net include:spf.protection.outlook.com include:spf.signhost.com -all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 8 of 10 DNS lookups #2
    SPF record needs 8 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.rocfriesepoort.nl)

Found

Record
v=DMARC1; p=none; rua=mailto:systeembeheer@rocfriesepoort.nl;
Found at
_dmarc.rocfriesepoort.nl
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:systeembeheer@rocfriesepoort.nlAggregate report addresses

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:systeembeheer@rocfriesepoort.nl
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

pass

Selectors: selector2, s1, s2

Found

Selectors
selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector2, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector2: RSA 2048 bits; s1: RSA 2048 bits; s2: 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 (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
49995
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

warn

No MX records found

Checks

  • !
    No MX records
    No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9
  • i
    Receives no mail but sends
    The domain has no MX records but its SPF record authorizes senders. If it does not send mail either, use "v=spf1 -all" and DMARC p=reject.
    #28

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