Mail domain report: megagadgets.nl

SPF

fail

SPF record published

Found

Record: v=spf1 mx a include:_spf.mailcampaigns.nl ~all
DNS lookups: 4 of 10
Void lookups: 0 of 2
Records published: 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 4 of 10 DNS lookups #2

SPF record needs 4 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.
✗

Multiple SPF records

Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.

#16
✓ 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.megagadgets.nl)

Found

Record: v=DMARC1; p=none; sp=none; rua=mailto:achmed@hypemedia.nl; ruf=mailto:achmed@hypemedia.nl; rf=afrf; pct=100; ri=86400
Found at: _dmarc.megagadgets.nl
External report address: mailto:achmed@hypemedia.nl (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:achmed@hypemedia.nl	Aggregate report addresses
ruf	mailto:achmed@hypemedia.nl	Failure report addresses
rf	afrf	Failure report format
ri	86400	Report interval (seconds)

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:achmed@hypemedia.nl
!

Report address not authorized

These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:achmed@hypemedia.nl (needs megagadgets.nl._report._dmarc.hypemedia.nl). Ask the report provider to publish the record, or check the address.

#29

DKIM

warn

Selectors: k1, s1, s2

Found

Selectors: k1, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: k1, s1, s2 #7

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

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

warn

Signed, but no DS at parent

Found

DNSKEY records: Yes (1)
DS at parent: No
Algorithms: RSASHA256 (8)
Key tags: 22357
Signatures valid until: 5 November 2026, 00:00 UTC

Checks

!

Signed, but no DS at parent

The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

#8
✓ Signatures valid until 2026-11-05 #21

DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	ASPMX.L.GOOGLE.COM	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5	ALT1.ASPMX.L.GOOGLE.COM	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5	ALT2.ASPMX.L.GOOGLE.COM	A 142.251.127.27 AAAA 2a00:1450:4010:c22::1a	lcfrai-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	ALT3.ASPMX.L.GOOGLE.COM	A 192.179.20.27 AAAA 2404:6800:4000:1027::1a	ncboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
10	ALT4.ASPMX.L.GOOGLE.COM	A 192.178.158.26 AAAA 2404:6800:4013:813::1a	lcdels-in-f26.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 5 MX records #9

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

Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
ASPMX.L.GOOGLE.COM	none	-
ALT1.ASPMX.L.GOOGLE.COM	none	-
ALT2.ASPMX.L.GOOGLE.COM	none	-
ALT3.ASPMX.L.GOOGLE.COM	none	-
ALT4.ASPMX.L.GOOGLE.COM	none	-

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