Mail domain report: linqhost.nl

SPF

pass

SPF record published

Found

Record: v=spf1 a include:servers.mcsv.net include:spf.mandrillapp.com mx ip4:178.128.241.83 a:i-mail-intern.linqhost.net include:_spf.paytsoftware.com include:_spf.google.com include:spf.zoho.eu include:eu.transmail.net ~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.linqhost.nl)

Found

Record: v=DMARC1; p=reject; rua=mailto:dmarc@linqhost.uriports.com; ruf=mailto:dmarc@linqhost.uriports.com; fo=1:d:s
Found at: _dmarc.linqhost.nl
External report address: mailto:dmarc@linqhost.uriports.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:dmarc@linqhost.uriports.com	Aggregate report addresses
ruf	mailto:dmarc@linqhost.uriports.com	Failure report addresses
fo	1:d:s	Failure reporting options

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@linqhost.uriports.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: mail, google, s1, s2

Found

Selectors: mail, google, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 4096 bits
google	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: mail, google, s1, s2 #7

DKIM keys found for this domain with selectors: mail, google, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: s2 (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

warn

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 62350, 17419
Signatures valid until: 29 October 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 expire in 154h0m0s

DNSKEY signatures expire at 2026-10-29T00:00:00Z (in 154h0m0s). Check that re-signing works.

#21

MX

warn

4 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx1.smtp.goog	A 216.239.32.151 AAAA 2001:4860:4802:32::97	no PTR no PTR
20	mx2.smtp.goog	A 216.239.34.151 AAAA 2001:4860:4802:34::97	no PTR no PTR
30	mx3.smtp.goog	A 216.239.36.151 AAAA 2001:4860:4802:36::97	no PTR no PTR
40	mx4.smtp.goog	A 216.239.38.151 AAAA 2001:4860:4802:38::97	no PTR no PTR

Checks

✓ 4 MX records #9

Found 4 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 4 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 4 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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 216.239.32.151 (mx1.smtp.goog), 2001:4860:4802:32::97 (mx1.smtp.goog), 216.239.34.151 (mx2.smtp.goog), 2001:4860:4802:34::97 (mx2.smtp.goog), 216.239.36.151 (mx3.smtp.goog), 2001:4860:4802:36::97 (mx3.smtp.goog), 216.239.38.151 (mx4.smtp.goog), 2001:4860:4802:38::97 (mx4.smtp.goog). Ask your hosting provider to set one.

#30

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 4 MX hosts

Found

MTA-STS record: v=STSv1; id=20240125115345Z;
Policy URL: https://mta-sts.linqhost.nl/.well-known/mta-sts.txt
Mode: testing
Allowed MX: mx4.smtp.goog, mx2.smtp.goog, mx3.smtp.goog, mx1.smtp.goog
Max age: 86400 seconds
TLS-RPT record: v=TLSRPTv1; rua=mailto:tlsrpt@linqhost.uriports.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.smtp.goog	none	-
mx2.smtp.goog	none	-
mx3.smtp.goog	none	-
mx4.smtp.goog	none	-

Checks

✓ Record published #32

MTA-STS record found with id 20240125115345Z.
!

Policy in testing mode

With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

#33
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
✓ Reports enabled #35

TLS reports are sent to: mailto:tlsrpt@linqhost.uriports.com
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