Mail domain report: blogger.de

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.forwardemail.net include:_spf.antville.org -all
DNS lookups: 10 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

warn

p=reject (_dmarc.blogger.de)

Found

Record: v=DMARC1; p=reject; pct=100; rua=mailto:dmarc-64240159b1be9d97db72a65c@forwardemail.net,mailto:re+r0rojdj0tr4@dmarc.postmarkapp.com; sp=none; aspf=r;
Found at: _dmarc.blogger.de
External report address: mailto:dmarc-64240159b1be9d97db72a65c@forwardemail.net (authorized)
External report address: mailto:re+r0rojdj0tr4@dmarc.postmarkapp.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-64240159b1be9d97db72a65c@forwardemail.net,mailto:re+r0rojdj0tr4@dmarc.postmarkapp.com	Aggregate report addresses
aspf	r	SPF alignment (r = relaxed, s = strict)

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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-64240159b1be9d97db72a65c@forwardemail.net, mailto:re+r0rojdj0tr4@dmarc.postmarkapp.com
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
✓ 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

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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx1.forwardemail.net	A 138.197.213.185 A 121.127.44.56 AAAA 2a02:6ea0:d71e::2 AAAA 2604:a880:2:d0::306:1	mx1.forwardemail.net ✓ mx1.forwardemail.net ✓ mx1.forwardemail.net ✓ mx1.forwardemail.net ✓
10	mx2.forwardemail.net	A 121.127.44.59 A 104.248.224.170 AAAA 2604:a880:400:d1::cd:9001 AAAA 2a02:6ea0:d71e::1	mx2.forwardemail.net ✓ mx2.forwardemail.net ✓ mx2.forwardemail.net ✓ mx2.forwardemail.net ✓

Checks

✓ 2 MX records #9

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

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.forwardemail.net	3 1 1 321f694ead3a2e73… 3 1 1 5e81da1af16df20b…	Yes
mx2.forwardemail.net	3 1 1 5e81da1af16df20b… 3 1 1 321f694ead3a2e73…	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 2 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