Mail domain report: yokogawa.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:192.28.158.195 ip4:192.28.158.196 ip4:199.15.215.25 ip4:199.15.215.26 ip4:199.15.215.83 ip4:199.15.215.84/31 ip4:199.15.215.86 ip4:210.160.226.240/31 ip4:20.210.48.173 ip4:20.89.31.78 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:204.220.160.0/21 include:spf.protection.outlook.com include:_spf.salesforce.com include:aspmx.pardot.com include:kairos3.com include:amazonses.com include:spf.servicecentral.com ~all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

Found

Record: v=DMARC1; p=quarantine; sp=none; rua=mailto:dmarc_agg@vali.email; ri=86400; adkim=r; aspf=r;
Found at: _dmarc.yokogawa.com
External report address: mailto:dmarc_agg@vali.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
rua	mailto:dmarc_agg@vali.email	Aggregate report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
ri	86400	Report interval (seconds)

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_agg@vali.email
!

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

Selectors: dkim, selector1, mx, s1

Found

Selectors: dkim, selector1, mx, s1
_domainkey: NOERROR

Selector	Key	Flags
dkim	RSA 2048 bits
selector1	RSA 1024 bits
mx	RSA 1024 bits
s1	RSA 2048 bits

Checks

✓ Keys found: dkim, selector1, mx, s1 #7

DKIM keys found for this domain with selectors: dkim, selector1, mx, s1
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), mx (1024 bits). Rotate to a 2048-bit key.

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

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
5	yokogawa-com.mail.protection.outlook.com	A 52.101.124.0 A 52.101.124.1 A 52.101.157.11 A 52.101.157.10 AAAA 2a01:111:f403:cc1f:: AAAA 2a01:111:f403:cc24:: AAAA 2a01:111:f403:cc1a::2 AAAA 2a01:111:f403:cc1a::1	mail-tycp286cu02600.inbound.protection.outlook.com ✓ mail-ty3p286cu00101.inbound.protection.outlook.com ✓ mail-os0p286cu01203.inbound.protection.outlook.com ✓ mail-os0p286cu01302.inbound.protection.outlook.com ✓ mail-os9p286cu00100.inbound.protection.outlook.com ✓ mail-os0p286cu01300.inbound.protection.outlook.com ✓ mail-tyvp286cu00302.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
yokogawa-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