rocmn.nl

Checked 22 October 2026, 15:41 UTC · via 8.8.8.8
✗Problems found
25 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:84.241.176.43 ip4:84.241.173.108 ip4:5.157.87.166 ip4:212.83.220.41 ip4:212.83.220.42 ip6:2001:4018:1404::1041 include:spf.protection.outlook.com ip4:37.97.250.30 ip4:193.172.33.120 ip4:193.172.33.122 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.145.0/24 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.177.0/24 ip4:198.2.178.0/23 ip4:198.2.180.0/24 include:spf1.rocmn.nl ~all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; rua=mailto:cf9l4vmf@rua.eu.dmarcmanager.app,mailto:postmaster@rocmn.nl; ruf=mailto:postmaster@rocmn.nl; fo=1;
Found at
_dmarc.rocmn.nl
External report address
mailto:cf9l4vmf@rua.eu.dmarcmanager.app (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:cf9l4vmf@rua.eu.dmarcmanager.app,mailto:postmaster@rocmn.nlAggregate report addresses
rufmailto:postmaster@rocmn.nlFailure report addresses
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:cf9l4vmf@rua.eu.dmarcmanager.app, mailto:postmaster@rocmn.nl
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

fail

Selectors: default, selector1, pm

Found

Selectors
default, selector1, pm
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
selector1RSA 1024 bits
pmRSA 768 bits

Checks

  • ✓ Keys found: default, selector1, pm #7
    DKIM keys found for this domain with selectors: default, selector1, pm
  • ✗
    Weak DKIM key
    RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): pm (768 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
48171, 3379
Signatures valid until
26 October 2026, 11:58 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 expire in 92h0m0s
    DNSKEY signatures expire at 2026-10-26T11:58:43Z (in 92h0m0s). Check that re-signing works.
    #21

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0rocmn-nl.mail.protection.outlook.comA 52.101.68.39 A 52.101.73.153 A 52.101.103.143 A 52.101.68.29 AAAA 2a01:111:f403:ca04::d AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca38::a AAAA 2a01:111:f403:ca04::10mail-db7pr03cu00607.inbound.protection.outlook.com ✓ mail-as8pr05cu00401.inbound.protection.outlook.com ✓ mail-miypr03cu00107.inbound.protection.outlook.com ✓ mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-wa4pr05cu00102.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
rocmn-nl.mail.protection.outlook.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