Mail domain report: youngcapital.nl

SPF

warn

SPF record published

Found

Record: v=spf1 ip4:198.21.4.52 ip4:167.89.31.27 ip4:40.92.0.0/15 ip4:185.46.182.1 ip4:192.174.90.95 ip4:52.49.4.76/32 ip4:52.49.5.90/32 ip4:69.72.32.0/20 ip4:3.222.0.24/29 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip4:3.93.157.0/24 ip4:62.148.182.10 ip4:62.148.182.12 ip4:62.148.191.63 ip4:166.78.68.0/22 ip4:167.89.127.244 ip4:44.192.35.0/24 ip4:3.210.190.0/24 include:_spf.google.com include:_spf0000000.youngcapital.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.
!

Broad IP ranges

These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15, ip4:52.100.0.0/15. Check that you really own and send from all of them.

#27

DMARC

warn

p=quarantine (_dmarc.youngcapital.nl)

Found

Record: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@youngcapital.nl; ruf=mailto:dmarc@youngcapital.nl; fo=1;aspf=r;adkim=r
Found at: _dmarc.youngcapital.nl

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc@youngcapital.nl	Aggregate report addresses
ruf	mailto:dmarc@youngcapital.nl	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	1	Failure 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@youngcapital.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: mail, k1, google

Found

Selectors: mail, k1, google
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
k1	RSA 1024 bits
google	RSA 2048 bits

Checks

✓ Keys found: mail, k1, google #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), 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: 25841, 9221
Signatures valid until: 22 October 2026, 02: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 5h0m0s

DNSKEY signatures expire at 2026-10-22T02:00:00Z (in 5h0m0s). 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.27 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
10	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
10	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
20	alt3.aspmx.l.google.com	A 192.179.20.26 AAAA 2404:6800:4000:1027::1b	ncboms-in-f26.1e100.net ✓ ncboms-in-f27.1e100.net ✓
20	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