Mail domain report: fischerverlage.de

SPF

warn

SPF record published

Found

Record: v=spf1 include:_spf.senders.scnem.com include:spf.mailjet.com include:_spf.google.com include:mailcontrol.com include:spfa.alinto.net include:r25.hallo.cloud ip4:193.194.144.165 ip4:94.130.131.29 ip4:85.115.56.190 ip4:85.115.54.190 a:smtpw.cytric.net ~all
DNS lookups: 7 of 10
Void lookups: 1 of 2
Problem: include:r25.hallo.cloud does not exist or has no records

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
!

7 of 10 DNS lookups, with problems

SPF record needs 7 DNS lookups (limit is 10). Problems found: include:r25.hallo.cloud does not exist or has no records.

#2
✓ 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.
!

1 void lookup

1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

#26
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.fischerverlage.de)

Found

Record: v=DMARC1;p=none;rua=mailto:dmarc-reports@fischerverlage.de;ruf=mailto:dmarc-reports@fischerverlage.de; fo=1:s
Found at: _dmarc.fischerverlage.de

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:dmarc-reports@fischerverlage.de	Aggregate report addresses
ruf	mailto:dmarc-reports@fischerverlage.de	Failure report addresses
fo	1:s	Failure reporting options

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:dmarc-reports@fischerverlage.de
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

pass

Selectors: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
google	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: google, s1, s2 #7

DKIM keys found for this domain with selectors: google, s1, s2
✓ Strong keys #23

DKIM keys are strong enough: google: RSA 2048 bits; s1: RSA 2048 bits; s2: RSA 2048 bits.
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
10	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 ✓
50	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
50	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 ✓
100	alt3.aspmx.l.google.com	A 192.179.20.26 AAAA 2404:6800:4000:1027::1a	ncboms-in-f26.1e100.net ✓ ncboms-in-f26.1e100.net ✓
100	alt4.aspmx.l.google.com	A 192.178.158.27 AAAA 2404:6800:4013:813::1a	lcdels-in-f27.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