Mail domain report: hoyoverse.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com -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

warn

p=quarantine (_dmarc.hoyoverse.com)

Found

Record: v=DMARC1;p=quarantine;rua=mailto:crm@hoyoverse.com
Found at: _dmarc.hoyoverse.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:crm@hoyoverse.com	Aggregate report addresses

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:crm@hoyoverse.com
✓ 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

fail

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NXDOMAIN

Checks

✗

No DKIM keys published

_domainkey.hoyoverse.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#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

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
5	hoyoverse-com.mail.protection.outlook.com	A 52.101.137.0 A 52.101.157.80 A 52.101.137.2 A 52.101.124.117 AAAA 2a01:111:f403:cc09:: AAAA 2a01:111:f403:cc09::1 AAAA 2a01:111:f403:cc1a::8 AAAA 2a01:111:f403:cc1f::4	mail-sg2pr03cu00500.inbound.protection.outlook.com ✓ mail-os8pr02cu00100.inbound.protection.outlook.com ✓ no PTR mail-tydpr03cu00105.inbound.protection.outlook.com ✓ mail-sg2pr03cu00500.inbound.protection.outlook.com ✓ no PTR mail-tydpr03cu00100.inbound.protection.outlook.com ✓ mail-os8pr02cu00104.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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (hoyoverse-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (hoyoverse-com.mail.protection.outlook.com). Ask your hosting provider to set one.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
hoyoverse-com.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

pass

https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.svg

Found

Record: v=BIMI1;l=https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.svg;a=https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.pem
Found at: default._bimi.hoyoverse.com
Logo: https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.svg
Certificate: https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.svg; certificate: https://vmc.digicert.com/51d5cc2b-b40d-422a-ab73-53b10d5ff816.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.