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.
What to do first
- 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.
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 security | 20/30 | Spoofing 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 infrastructure | 3/15 | The domain's infrastructure lacks basic protections. |
Fix priorities
- 1.HighSPF — who may send mail for the domain · Hardening gap+22
- 2.MediumDNSSEC — signed DNS records · Hardening gap+16
- 3.LowCAA — who may issue certificates · Hardening gap+11
Findings
SPF — who may send mail for the domain
Failed · Severity: High · Hardening gap · 0/10There 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.
(no SPF record found)
$ dig +short TXT mizuhobank.co.jp
- Map every service that sends mail in the domain's name (Google Workspace / Microsoft 365, newsletter tool, CRM).
- Publish exactly one TXT record at the domain root starting with v=spf1.
- 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.
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
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
DKIM — digital signature on email
Passed · Severity: OK · 5/5A 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.
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
MX — inbound mail routing
Info · Severity: OK · unscoredNo 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.
(no MX records)
$ dig +short MX mizuhobank.co.jp
- 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.
HTTPS available
Not applicable · Severity: OK · Not applicableThe 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.
No A/AAAA record for the domain
$ curl -svI https://mizuhobank.co.jp/ 2>&1 | grep -E "SSL|HTTP|expire"
HTTP → HTTPS redirect
Not applicable · Severity: OK · Not applicableThe 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.
Not checked
$ curl -sI http://mizuhobank.co.jp/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Not applicable · Severity: OK · Not applicableThe 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.
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
HSTS — enforce encryption in the browser
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
CSP — protection from script injection
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Clickjacking protection
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
X-Content-Type-Options
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Referrer-Policy
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
Permissions-Policy
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://mizuhobank.co.jp/
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The 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.
AD = false DS mizuhobank.co.jp: NODATA
$ dig +short DS mizuhobank.co.jp
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- 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.
CAA — who may issue certificates
Needs attention · Severity: Low · Hardening gap · 0/5Any 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.
(no CAA records found)
$ dig +short CAA mizuhobank.co.jp
- Identify which certificate authority issued your current certificate (see the certificate check).
- 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.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
6 NS servers.
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
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
| A | mizuhobank.co.jp | — |
| AAAA | mizuhobank.co.jp | — |
| MX | mizuhobank.co.jp | — |
| 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 |
| TXT | mizuhobank.co.jp | GpJdLbNj4m1pL1CiWpxBPCvtME3P1C | _mot0w42x6rwti5jlse2jk1mwboexdcy | apple-domain-verification=N852TjDhjRgEQ4IU | apple-domain-verification=AgjbGlb3k4Dup4zZO2przt6pguJsumbmE5wUOuwnjM0 |
| 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 |
| CAA | mizuhobank.co.jp | — |
| DS | mizuhobank.co.jp | — |