Mail domain report: metabolic.nl

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:spf.mandrillapp.com ~all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 2 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

fail

p=none (_dmarc.metabolic.nl)

Found

Record: v=DMARC1; p=none; rua=mailto:reports@debuginc.com; adkim=s; aspf=s; pct=0;
Found at: _dmarc.metabolic.nl
External report address: mailto:reports@debuginc.com (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
pct	0	Percentage of mail the policy applies to
rua	mailto:reports@debuginc.com	Aggregate report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)

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:reports@debuginc.com
!

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:reports@debuginc.com (needs metabolic.nl._report._dmarc.debuginc.com). Ask the report provider to publish the record, or check the address.

#29

DKIM

warn

Selectors: k1, google

Found

Selectors: k1, google
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits
google	RSA 2048 bits

Checks

✓ Keys found: k1, google #7

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

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, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 27858, 2040
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 153h0m0s

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

#21

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	ASPMX.L.GOOGLE.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5	ALT1.ASPMX.L.GOOGLE.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1a	rd-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
5	ALT2.ASPMX.L.GOOGLE.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10	ASPMX2.GOOGLEMAIL.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
10	ASPMX3.GOOGLEMAIL.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-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

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

Found

MTA-STS record: v=STSv1; id=202403121211;
Policy URL: https://mta-sts.metabolic.nl/.well-known/mta-sts.txt
Mode: testing
Allowed MX: aspmx.l.google.com, aspmx3.googlemail.com, alt1.aspmx.l.google.com, aspmx2.googlemail.com, alt2.aspmx.l.google.com
Max age: 604800 seconds
TLS-RPT record: v=TLSRPTv1; rua=mailto:reports@debuginc.com;

DANE (TLSA records)

MX host	TLSA	DNSSEC
ASPMX.L.GOOGLE.com	none	-
ALT1.ASPMX.L.GOOGLE.com	none	-
ALT2.ASPMX.L.GOOGLE.com	none	-
ASPMX2.GOOGLEMAIL.com	none	-
ASPMX3.GOOGLEMAIL.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 202403121211.
!

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:reports@debuginc.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