ms-ins.com

Checked 22 October 2026, 09:53 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:42.125.207.184 ip4:124.146.170.8/32 ip4:124.146.170.9/32 include:spf.ms-ins.com include:digi-mel.jp include:spf0062.mediagalaxy.ne.jp include:hagaki.dejibin.com include:cust-spf.exacttarget.com include:spf.smktg.jp include:_spf.salesforce.com include:spf.tricorn.net ~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

fail

p=none (_dmarc.ms-ins.com)

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc_fncm@ms-ins.net; ruf=mailto:dmarc_fncm@ms-ins.net
Found at
_dmarc.ms-ins.com
External report address
mailto:dmarc_fncm@ms-ins.net (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc_fncm@ms-ins.netAggregate report addresses
rufmailto:dmarc_fncm@ms-ins.netFailure report addresses

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_fncm@ms-ins.net
  • ✓ 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

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mskigw22.index.or.jpA 133.250.164.183mskigw22.index.or.jp ✓
10mskigw23.index.or.jpA 133.250.164.187mskigw23.index.or.jp ✓
10mskigw24.index.or.jpA 133.250.164.188mskigw24.index.or.jp ✓
20mskigw21.index.or.jpA 133.250.164.182mskigw21.index.or.jp ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mskigw22.index.or.jp, mskigw23.index.or.jp, mskigw24.index.or.jp, mskigw21.index.or.jp
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mskigw22.index.or.jpnone-
mskigw23.index.or.jpnone-
mskigw24.index.or.jpnone-
mskigw21.index.or.jpnone-

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