SurfaceMap › s › shiseido.com

shiseido.com

Checked 2026-10-22 10:41 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

fail

20 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers iSOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns-c.iij.ad.jp (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:50028->[2001:240:bb81::29:111]:53: read: connection reset by peer; ns020-5v9al5v9m6b83k5i.5.d-53.jp (2001:240:bb81::29:1111): read tcp [2a01:4f8:1c1c:eebf::1]:34464->[2001:240:bb81::29:1111]:53: read: connection reset by peer; ns020-5v9al5v9m6b83k5i.5.d-53.org (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:50040->[2001:240:bb81::29:111]:53: read: connection reset by peer.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns-b.iij.ad.jp, dns-c.iij.ad.jp; only in the zone: ns020-5v9al5v9m6b83k5i.5.d-53.info, ns020-5v9al5v9m6b83k5i.5.d-53.jp, ns020-5v9al5v9m6b83k5i.5.d-53.org. dns-b.iij.ad.jp, dns-c.iij.ad.jp, ns020-5v9al5v9m6b83k5i.5.d-53.info, ns020-5v9al5v9m6b83k5i.5.d-53.jp, ns020-5v9al5v9m6b83k5i.5.d-53.org report NS ns020-5v9al5v9m6b83k5i.5.d-53.info ns020-5v9al5v9m6b83k5i.5.d-53.jp ns020-5v9al5v9m6b83k5i.5.d-53.org.
    #7
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for shiseido.com ›

Mail

warn

22 passed 7 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), mail (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (shiseido-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (shiseido-com.mail.protection.outlook.com). Ask your hosting provider to set one.
    #30
  • !
    Not configured
    TLS · 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

Recent checks

!

Full report

Mail report for shiseido.com ›