lochem.nl

Checked 22 October 2026, 14:11 UTC · via 8.8.8.8
!Passed with warnings
26 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a ip4:80.113.67.242/28 ip4:194.151.65.17/28 ip4:90.145.221.223 ip4:195.143.61.129 ip4:193.163.108.129 include:_spf.zivver.com include:spf.pinkprivate.cloud include:_spf.services.centric.eu include:spf.eprov.nl include:spf.topdesk.net include:de._netblocks.mimecast.com include:spf.protection.outlook.com include:spf.afas.online -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.lochem.nl)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@lochem.nl; ruf=mailto:dmarc@lochem.nl; fo=s
Found at
_dmarc.lochem.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@lochem.nlAggregate report addresses
rufmailto:dmarc@lochem.nlFailure report addresses
fosFailure 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:dmarc@lochem.nl
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: k1

Found

Selectors
k1
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 1024 bits

Checks

  • ✓ Keys found: k1 #7
    DKIM keys found for this domain with selectors: k1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: k1 (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 (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
48051, 24190
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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10de-smtp-inbound-1.mimecast.comA 194.104.108.22 A 194.104.110.22de-smtp-inbound-1.mimecast.com ✓ de-smtp-inbound-1.mimecast.com ✓
10de-smtp-inbound-2.mimecast.comA 194.104.110.22 A 194.104.108.22de-smtp-inbound-1.mimecast.com ✓ de-smtp-inbound-2.mimecast.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
de-smtp-inbound-1.mimecast.comnone-
de-smtp-inbound-2.mimecast.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