roermond.nl

Checked 22 October 2026, 15:41 UTC · via 8.8.8.8
!Passed with warnings
27 passed 3 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:45.80.232.20/30 ip4:45.130.217.191 ip4:85.90.85.193 ip4:20.50.169.50 ip4:85.90.85.177 ip4:185.46.182.200/29 ip4:54.240.0.0/18 ip4:185.46.182.208/31 ip4:195.35.139.57 ip4:87.249.99.173 ip4:217.114.107.191 ip4:87.249.113.154 ip4:194.187.45.0/26 ip4:81.246.113.50 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:212.72.62.129/27 ip4:91.218.37.0/24 ip4:185.71.125.0/24 ip4:185.71.127.0/24 ip4:185.71.124.0/24 ip4:78.41.77.211 ip4:185.46.182.1 ip4:20.82.87.96/28 ip4:176.74.239.242 ip4:213.208.232.101 ip6:2a07:cb84:3075:912:10:10:159:25 ip6:2a07:cb81:3711:815:10:10:160:25 a:malengo.exception.mx include:spf.protection.outlook.com include:spf.topdesk.net include:_spf.axxerion.com include:_spf.mail.services.bastion365.net include:spf.mediamens.nl include:spf.simgroephosting.nl include:spf.tribecrm.nl -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.roermond.nl)

Found

Record
v=DMARC1; p=reject; rua=mailto:clhnvn7p@ag.eu.dmarcadvisor.com,mailto:ewpi85jr@ag.eu.dmarcadvisor.com; ruf=mailto:dmarcadmin@ictnml.nl
Found at
_dmarc.roermond.nl
External report address
mailto:clhnvn7p@ag.eu.dmarcadvisor.com (authorized)
External report address
mailto:ewpi85jr@ag.eu.dmarcadvisor.com (authorized)
External report address
mailto:dmarcadmin@ictnml.nl (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:clhnvn7p@ag.eu.dmarcadvisor.com,mailto:ewpi85jr@ag.eu.dmarcadvisor.comAggregate report addresses
rufmailto:dmarcadmin@ictnml.nlFailure 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:clhnvn7p@ag.eu.dmarcadvisor.com, mailto:ewpi85jr@ag.eu.dmarcadvisor.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2 #7
    DKIM keys found for this domain with selectors: selector1, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ 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
ECDSAP384SHA384 (14)
Key tags
63711
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

1 mail server

Found

PriorityHostRecordsReverse DNS
10roermond-nl.mail.protection.outlook.comA 52.101.68.12 A 52.101.68.39 A 52.101.103.140 A 52.101.91.153 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca3c::6 AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca04::10mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-db7pr03cu00607.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-zrxpr04cu00106.inbound.protection.outlook.com ✓ mail-miypr02cu00202.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
roermond-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