Mail domain report: smbc-card.com

SPF

info

SPF record published

Found

Record: v=spf1 redirect=smbc-card.com.r.spf25.jp
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 6 DNS lookups (limit is 10).
i

Delegated via redirect

SPF record has no 'all' mechanism but redirects to smbc-card.com.r.spf25.jp, whose policy applies.

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

pass

p=reject (_dmarc.smbc-card.com)

Found

Record: v=DMARC1; p=reject; sp=quarantine; rua=mailto:smbccard00001-ra@dmarc25.jp,mailto:dmarc-rua@report.securemx.jp
Found at: _dmarc.smbc-card.com
External report address: mailto:smbccard00001-ra@dmarc25.jp (authorized)
External report address: mailto:dmarc-rua@report.securemx.jp (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	quarantine	Subdomain policy
rua	mailto:smbccard00001-ra@dmarc25.jp,mailto:dmarc-rua@report.securemx.jp	Aggregate report addresses

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:smbccard00001-ra@dmarc25.jp, mailto:dmarc-rua@report.securemx.jp
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ 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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 16525, 60241
Signatures valid until: 15 November 2026, 05:41 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2026-11-15 #21

DNSKEY signatures are valid until 2026-11-15T05:41:07Z.

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	mx.securemx.jp	A 210.130.202.92 A 210.130.202.93 A 210.130.202.96 A 210.130.202.99	mx180b.securemx.jp ✓ mx114b.securemx.jp ✓ mx114a.securemx.jp ✓ mx180a.securemx.jp ✓

Checks

✓ 1 MX record #9

Found 1 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mx.securemx.jp

#11
!

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 4 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
mx.securemx.jp	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://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.svg

Found

Record: v=BIMI1; l=https://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.svg; a=https://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.pem
Found at: default._bimi.smbc-card.com
Logo: https://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.svg
Certificate: https://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.svg; certificate: https://www.smbc-card.com/common/dynamic/memx/img/mail_icon/logo_smcc.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.