Back to results

Digital exposure report

mizuhobank.co.jp

Critical findings in the observed public configuration. Some basic protections were not detected.

Scanned: 2026-11-20 07:30 UTC

Full coverage: every applicable check was assessed.

F
51/100

What to do first

  1. 1.

    List the servers allowed to send your email

    Without this list, it is easier for others to send email that looks like it came from you.

    Who can fix it: Your email provider, together with whoever manages your DNS

    How to verify after the fix

    dig +short TXT mizuhobank.co.jp
  2. 2.

    Turn on DNS signing for your domain

    Signing helps resolvers detect forged answers about your domain.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short DS mizuhobank.co.jp

A starting point, not a security guarantee.

What this grade means

Tested hostname
mizuhobank.co.jp
Website request
GET https://mizuhobank.co.jp/(no HTTPS response)
Scan time
2026-11-20 07:30:39 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • HTTPS available · Not applicable
  • HTTP → HTTPS redirect · Not applicable
  • SSL/TLS certificate validity · Not applicable
  • HSTS — enforce encryption in the browser · Not applicable
  • CSP — protection from script injection · Not applicable
  • Clickjacking protection · Not applicable
  • X-Content-Type-Options · Not applicable
  • Referrer-Policy · Not applicable
  • Permissions-Policy · Not applicable

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security20/30Spoofing email in the company's name is possible in some cases.
Encryption & certificate—Not applicable to this domain.
Browser protections—Not applicable to this domain.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.HighSPF — who may send mail for the domain · Hardening gap+22
  2. 2.MediumDNSSEC — signed DNS records · Hardening gap+16
  3. 3.LowCAA — who may issue certificates · Hardening gap+11

Findings

SPF — who may send mail for the domain

Failed · Severity: High · Hardening gap · 0/10

There is no list of servers authorized to send mail, making it easier to forge email in the company's name.

No v=spf1 TXT record at the domain root. Receiving servers cannot validate the sender's IP address.

Source data: DNS TXT mizuhobank.co.jp
(no SPF record found)
$ dig +short TXT mizuhobank.co.jp
Fix recommendation (effort: Easy)
  1. Map every service that sends mail in the domain's name (Google Workspace / Microsoft 365, newsletter tool, CRM).
  2. Publish exactly one TXT record at the domain root starting with v=spf1.
  3. Start with ~all, and move to -all once DMARC reports confirm all legitimate senders are covered.
mizuhobank.co.jp.  TXT  "v=spf1 include:_spf.google.com ~all"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. An incorrect record can block legitimate mail — add every sender before tightening.

Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.mizuhobank.co.jp
v=DMARC1; p=reject; sp=reject; pct=100;fo=1;rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:mizuhobank00001-ra@dmarc25.jp; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
$ dig +short TXT _dmarc.mizuhobank.co.jp
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.

DKIM public key found for selector: s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.mizuhobank.co.jp
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqtF+TWTheGjBNXkpLRXZsLeHmi8ku68v…
s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDIhItkvqh9Lrb35CqwZtdt0ubAwmxcEZLQpISt…
$ dig +short TXT s1._domainkey.mizuhobank.co.jp
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Info · Severity: OK · unscored

No MX records are published. On its own this doesn't prove the domain can't receive email.

Without MX, senders may fall back to the A/AAAA address (RFC 5321 §5.1). A Null MX is appropriate only once you've confirmed the domain receives no email.

Source data: DNS MX mizuhobank.co.jp
(no MX records)
$ dig +short MX mizuhobank.co.jp
Fix recommendation (effort: Easy)
  1. Only if you've confirmed the domain receives no email: publish a Null MX (MX 0 .), and keep SPF -all and DMARC p=reject if it also sends none.
mizuhobank.co.jp.  MX  0 .

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain.

Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: HTTPS GET https://mizuhobank.co.jp/
No A/AAAA record for the domain
$ curl -svI https://mizuhobank.co.jp/ 2>&1 | grep -E "SSL|HTTP|expire"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: HTTP GET http://mizuhobank.co.jp/ (redirects not followed)
Not checked
$ curl -sI http://mizuhobank.co.jp/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: Certificate Transparency logs (certspotter) for mizuhobank.co.jp
No valid certificate found in CT logs
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect mizuhobank.co.jp:443 -servername mizuhobank.co.jp 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://mizuhobank.co.jp/
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://mizuhobank.co.jp/
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://mizuhobank.co.jp/
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://mizuhobank.co.jp/
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://mizuhobank.co.jp/
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://mizuhobank.co.jp/
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS mizuhobank.co.jp: NODATA
$ dig +short DS mizuhobank.co.jp
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec mizuhobank.co.jp SOA
delv mizuhobank.co.jp

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA mizuhobank.co.jp
(no CAA records found)
$ dig +short CAA mizuhobank.co.jp
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
mizuhobank.co.jp.  CAA  0 issue "letsencrypt.org"
mizuhobank.co.jp.  CAA  0 iodef "mailto:security@mizuhobank.co.jp"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

6 NS servers.

Source data: DNS NS mizuhobank.co.jp
dns002b.m-waas.jp
ns008-bnlbzvllhwtxintz.b.d-53.jp
ns008-bnlbzvllhwtxintz.b.d-53.net
ns008-bnlbzvllhwtxintz.b.d-53.info
dns001b.m-waas.jp
dns002a.m-waas.jp
$ dig +short NS mizuhobank.co.jp
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rules1 observed gaps
  • PCI DSS v4.0Not applicable
  • NIS2 / vendor due diligence3 observed gaps
  • SOC 2 / ISO 27001 baseline1 observed gaps

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Amizuhobank.co.jp—
AAAAmizuhobank.co.jp—
MXmizuhobank.co.jp—
NSmizuhobank.co.jpdns002b.m-waas.jp | ns008-bnlbzvllhwtxintz.b.d-53.jp | ns008-bnlbzvllhwtxintz.b.d-53.net | ns008-bnlbzvllhwtxintz.b.d-53.info | dns001b.m-waas.jp | dns002a.m-waas.jp
TXTmizuhobank.co.jpGpJdLbNj4m1pL1CiWpxBPCvtME3P1C | _mot0w42x6rwti5jlse2jk1mwboexdcy | apple-domain-verification=N852TjDhjRgEQ4IU | apple-domain-verification=AgjbGlb3k4Dup4zZO2przt6pguJsumbmE5wUOuwnjM0
TXT_dmarc.mizuhobank.co.jpv=DMARC1; p=reject; sp=reject; pct=100;fo=1;rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:mizuhobank00001-ra@dmarc25.jp; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
CAAmizuhobank.co.jp—
DSmizuhobank.co.jp—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain