Mail domain report: jiji.com

SPF

pass

SPF record published

Found

Record: v=spf1 +ip4:210.164.31.192/26 +ip4:210.158.210.0/23 +ip4:52.193.26.38 +ip4:52.198.42.254 +ip4:210.140.246.0/26 +ip4:210.152.253.76/26 include:spf.protection.outlook.com include:spf.spcloud.jp include:spf-bma.mpme.jp include:spf-rmb.mpme.jp include:fc4082.cuenote.jp include:amazonses.com -all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 7 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.jiji.com)

Found

Record: v=DMARC1; p=none; rua=mailto:dmarc-rua@jiji.com; ruf=mailto:dmarc-ruf@jiji.com; pct=100; adkim=r; aspf=r;
Found at: _dmarc.jiji.com

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-rua@jiji.com	Aggregate report addresses
ruf	mailto:dmarc-ruf@jiji.com	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

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-rua@jiji.com
✓ 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.jiji.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
0	jiji-com.mail.protection.outlook.com	A 52.101.157.11 A 52.101.157.10 A 52.101.124.5 A 52.101.124.6 AAAA 2a01:111:f403:cc1a::2 AAAA 2a01:111:f403:cc24:: AAAA 2a01:111:f403:cc1a:: AAAA 2a01:111:f403:cc1a::1	mail-os0p286cu01203.inbound.protection.outlook.com ✓ mail-os0p286cu01302.inbound.protection.outlook.com ✓ mail-tyvp286cu00305.inbound.protection.outlook.com ✓ mail-tyvp286cu00206.inbound.protection.outlook.com ✓ mail-tyvp286cu00302.inbound.protection.outlook.com ✓ mail-os0p286cu01300.inbound.protection.outlook.com ✓ mail-tycp286cu02600.inbound.protection.outlook.com ✓ mail-ty3p286cu00101.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
jiji-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

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