Digital exposure report
oups.ac.jp
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-17 23:03 UTC
Partial coverage: the score is based on 88% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.oups.ac.jp
- 2.
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 oups.ac.jp
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- oups.ac.jp
- Website request
- GET https://oups.ac.jp/(no HTTPS response)
- Scan time
- 2026-11-17 23:03:14 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
- 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 | 0/25 | An attacker can send email that looks like it came from the company. |
| 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+25
- 2.HighDMARC — anti-spoofing policy · Hardening gap+38
- 3.MediumDNSSEC — signed DNS records · Hardening gap+18
- 4.LowCAA — who may issue certificates · Hardening gap+13
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- DKIM — digital signature on email
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 oups.ac.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.
oups.ac.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
Failed · Severity: High · Hardening gap · 0/15No policy tells mail servers to block forged email in the company's name — a common opening for CEO fraud and phishing.
No TXT record at _dmarc.oups.ac.jp. Without DMARC, mail failing SPF/DKIM may still reach the inbox.
(no DMARC record found)
$ dig +short TXT _dmarc.oups.ac.jp
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.oups.ac.jp. TXT "v=DMARC1; p=none; rua=mailto:dmarc@oups.ac.jp; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.oups.ac.jp
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 host1.oups.ac.jp
$ dig +short MX oups.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://oups.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://oups.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 oups.ac.jp:443 -servername oups.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://oups.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://oups.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://oups.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://oups.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://oups.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://oups.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 oups.ac.jp: NODATA
$ dig +short DS oups.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 oups.ac.jp SOA delv oups.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 oups.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.
oups.ac.jp. CAA 0 issue "letsencrypt.org" oups.ac.jp. CAA 0 iodef "mailto:security@oups.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.
2 NS servers.
managed-ns02.mcnet.ad.jp managed-ns01.mcnet.ad.jp
$ dig +short NS oups.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 rules2 observed gaps · 1 unverified
- PCI DSS v4.0Not applicable
- NIS2 / vendor due diligence4 observed gaps
- SOC 2 / ISO 27001 baseline2 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 | oups.ac.jp | — |
| AAAA | oups.ac.jp | — |
| MX | oups.ac.jp | 10 host1.oups.ac.jp |
| NS | oups.ac.jp | managed-ns02.mcnet.ad.jp | managed-ns01.mcnet.ad.jp |
| TXT | oups.ac.jp | f28itv24dkbevd3ogc2re137kd |
| TXT | _dmarc.oups.ac.jp | — |
| CAA | oups.ac.jp | — |
| DS | oups.ac.jp | — |