Mail domain report: azubiyo.de

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:spf.funkemedien.de a a:sslout.df.eu ip4:80.82.206.0/26 ip4:212.224.100.197/32 ip4:212.224.100.196/32 -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=quarantine (_dmarc.azubiyo.de)

Found

Record: v=DMARC1; p=quarantine; sp=none; pct=100; rua=mailto:dmarc_report@funkemedien.de; ruf=mailto:dmarc_report_ruf@funkemedien.de; fo=1
Found at: _dmarc.azubiyo.de
External report address: mailto:dmarc_report@funkemedien.de (authorized)
External report address: mailto:dmarc_report_ruf@funkemedien.de (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc_report@funkemedien.de	Aggregate report addresses
ruf	mailto:dmarc_report_ruf@funkemedien.de	Failure report addresses
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_report@funkemedien.de
!

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

fail

Selectors: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
default	RSA 768 bits	test mode (t=y)
dkim	RSA 768 bits	test mode (t=y)
mail	RSA 768 bits	test mode (t=y)
email	RSA 768 bits	test mode (t=y)
k1	RSA 768 bits	test mode (t=y)
selector1	RSA 2048 bits
google	RSA 768 bits	test mode (t=y)
zoho	RSA 768 bits	test mode (t=y)
mx	RSA 768 bits	test mode (t=y)
key	RSA 768 bits	test mode (t=y)
mta	RSA 768 bits	test mode (t=y)
pm	RSA 768 bits	test mode (t=y)
dkim-smtp	RSA 768 bits	test mode (t=y)
s1	RSA 768 bits	test mode (t=y)
s2	RSA 768 bits	test mode (t=y)

Checks

✓ Keys found: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7

DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
✗

Weak DKIM key

RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): default (768 bits), dkim (768 bits), mail (768 bits), email (768 bits), k1 (768 bits), google (768 bits), zoho (768 bits), mx (768 bits), key (768 bits), mta (768 bits), pm (768 bits), dkim-smtp (768 bits), s1 (768 bits), s2 (768 bits). Rotate to a 2048-bit key.

#23
!

Key in test mode

These keys have t=y, so receivers treat DKIM failures as a test: default, dkim, mail, email, k1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2. Remove t=y once DKIM works.

#24

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

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	azubiyo-de.mail.protection.outlook.com	A 52.101.103.140 A 52.101.103.143 A 52.101.68.25 A 52.101.91.159 AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca21::c AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca04::a	mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-miypr03cu00107.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-du0pr03cu00102.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 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.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

Found 1 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 0 of 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
azubiyo-de.mail.protection.outlook.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