Digital exposure report
ouhs.ac.jp
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-17 23:03 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
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 ouhs.ac.jp
- 2.
Choose which companies may issue certificates for your domain
This reduces the chance of a certificate being issued by a provider you did not choose.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short CAA ouhs.ac.jp
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- ouhs.ac.jp
- Website request
- GET https://ouhs.ac.jp/(no HTTPS response)
- Scan time
- 2026-11-17 23:03:14 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 | 27/30 | Spoofing email from this domain is hard. |
| 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.MediumDNSSEC — signed DNS records · Hardening gap+16
- 2.LowCAA — who may issue certificates · Hardening gap+11
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 1 of 10 DNS lookups.
v=spf1 include:_spf.google.com ~all
$ dig +short TXT ouhs.ac.jp
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; rua=mailto:dmarc@ouhs.ac.jp
$ dig +short TXT _dmarc.ouhs.ac.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: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnNtrayaHaBFHAhdZo+OfqHbEUjgv…
$ dig +short TXT google._domainkey.ouhs.ac.jp
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 alt3.aspmx.l.google.com 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com
$ dig +short MX ouhs.ac.jp
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://ouhs.ac.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://ouhs.ac.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 ouhs.ac.jp:443 -servername ouhs.ac.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://ouhs.ac.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://ouhs.ac.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://ouhs.ac.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://ouhs.ac.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://ouhs.ac.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://ouhs.ac.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 ouhs.ac.jp: NODATA
$ dig +short DS ouhs.ac.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 ouhs.ac.jp SOA delv ouhs.ac.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 ouhs.ac.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.
ouhs.ac.jp. CAA 0 issue "letsencrypt.org" ouhs.ac.jp. CAA 0 iodef "mailto:security@ouhs.ac.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.
5 NS servers.
ns4.ouhs.ac.jp dns-x.sinet.ad.jp ns1.ouhs.ac.jp ns2.ouhs.ac.jp ns3.ouhs.ac.jp
$ dig +short NS ouhs.ac.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 rulesNo gaps observed
- PCI DSS v4.0Not applicable
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baselineNo gaps observed
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 | ouhs.ac.jp | — |
| AAAA | ouhs.ac.jp | — |
| MX | ouhs.ac.jp | 10 alt3.aspmx.l.google.com | 1 aspmx.l.google.com | 5 alt2.aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 10 alt4.aspmx.l.google.com |
| NS | ouhs.ac.jp | ns4.ouhs.ac.jp | dns-x.sinet.ad.jp | ns1.ouhs.ac.jp | ns2.ouhs.ac.jp | ns3.ouhs.ac.jp |
| TXT | ouhs.ac.jp | google-site-verification=fu6MUDqCGMLj9FdVADjXB4H_sSPSUrnEkdSENn65ydk | v=spf1 include:_spf.google.com ~all | MS=393B0816618ED83526FD5C50FE2390E02287C622 |
| TXT | _dmarc.ouhs.ac.jp | v=DMARC1; p=quarantine; rua=mailto:dmarc@ouhs.ac.jp |
| CAA | ouhs.ac.jp | — |
| DS | ouhs.ac.jp | — |