Mail domain report: jpberlin.de

SPF

pass

SPF record published

Found

Record: v=spf1 mx include:_spf.jpberlin.de ~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.jpberlin.de)

Found

Record: v=DMARC1; p=none; sp=none; adkim=r; aspf=r; pct=100; rua=mailto:abuse+arf@heinlein-support.de; rf=afrf; fo=1;
Found at: _dmarc.jpberlin.de
External report address: mailto:abuse+arf@heinlein-support.de (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:abuse+arf@heinlein-support.de	Aggregate report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	1	Failure reporting options
rf	afrf	Failure report format

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:abuse+arf@heinlein-support.de
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NOERROR

Checks

!

No key under common selectors

The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

#7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (3)
DS at parent: Yes
Algorithms: RSASHA512 (10)
Key tags: 32276, 18597, 8845
Signatures valid until: 12 November 2026, 05:45 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-12 #21

DNSKEY signatures are valid until 2026-11-12T05:45:03Z.

MX

warn

4 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx1.jpberlin.de	A 91.198.250.10	mx1.heinlein-support.de ✓
10	mx2.jpberlin.de	A 91.198.250.20	mx2.heinlein-support.de ✓
20	mx3.jpberlin.de	A 91.198.250.30	mx3.heinlein-support.de ✓
50	mx-n.jpberlin.de	A 91.198.250.16	mx-n.jpberlin.de ✓

Checks

✓ 4 MX records #9

Found 4 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: mx1.jpberlin.de, mx2.jpberlin.de, mx3.jpberlin.de, mx-n.jpberlin.de

#11
✓ 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.
✓ 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 4 of 4 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.jpberlin.de	3 1 1 3fb24e3ee20fd8b0… 3 0 1 e3e75b6af498e3e4… 3 1 1 6b0dd472d3c50d1e… 3 1 1 24ccece42f79393a… 3 1 1 6966e242c245602e… 3 1 1 d02a3063f3ce3839… 3 1 1 e3b0c44298fc1c14…	Yes
mx2.jpberlin.de	3 1 1 d02a3063f3ce3839… 3 1 1 24ccece42f79393a… 3 0 1 e3e75b6af498e3e4… 3 1 1 8f7cd09562ffc3ac… 3 1 1 6b0dd472d3c50d1e…	Yes
mx3.jpberlin.de	3 1 1 70dc6f62943b0320… 3 0 1 e3e75b6af498e3e4… 3 1 1 c36a0b082b3354e3… 3 1 1 24ccece42f79393a… 3 1 1 6b0dd472d3c50d1e… 3 1 1 d02a3063f3ce3839…	Yes
mx-n.jpberlin.de	3 1 1 3fb24e3ee20fd8b0… 3 1 1 6b0dd472d3c50d1e…	Yes

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ DANE on all MX hosts #36

All 4 MX hosts publish DNSSEC-validated TLSA records.

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