Digital exposure report
kyokyo-u.ac.jp
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-21 20:03 UTC
Full coverage: every applicable check was assessed.
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.kyokyo-u.ac.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 kyokyo-u.ac.jp
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- kyokyo-u.ac.jp
- Website request
- GET https://kyokyo-u.ac.jp/(no HTTPS response)
- Scan time
- 2026-11-21 20:03:42 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 | 15/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 | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighDMARC — anti-spoofing policy · Hardening gap+33
- 2.MediumDNSSEC — signed DNS records · Hardening gap+16
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 4 of the 10 allowed DNS lookups.
v=spf1 include:spf.kyokyo-u.ac.jp include:_spf.google.com include:spf.protection.outlook.com include:spf.haihaimail.jp -all
$ dig +short TXT kyokyo-u.ac.jp
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.kyokyo-u.ac.jp. Without DMARC, mail failing SPF/DKIM may still reach the inbox.
(no DMARC record found)
$ dig +short TXT _dmarc.kyokyo-u.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.kyokyo-u.ac.jp. TXT "v=DMARC1; p=none; rua=mailto:dmarc@kyokyo-u.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
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, selector1, selector2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAi/sqN+PmnnhuHGXCBKy0hGrYqBWk… selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCS/JWAt8x+sb0jK0O0MhrMqHhnqXJeTI1h… selector2._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCvGU4pfS3a2dz3czVabfJx509DtnwH932G…
$ dig +short TXT google._domainkey.kyokyo-u.ac.jp
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mailrelay2.kyokyo-u.ac.jp 10 mailrelay1.kyokyo-u.ac.jp
$ dig +short MX kyokyo-u.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://kyokyo-u.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://kyokyo-u.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 kyokyo-u.ac.jp:443 -servername kyokyo-u.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://kyokyo-u.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://kyokyo-u.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://kyokyo-u.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://kyokyo-u.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://kyokyo-u.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://kyokyo-u.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 kyokyo-u.ac.jp: NODATA
$ dig +short DS kyokyo-u.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 kyokyo-u.ac.jp SOA delv kyokyo-u.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
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "secomtrust.net" | 0 issuewild ";" | 0 issuemail "secomtrust.net" | 0 iodef "mailto:noc@kyokyo-u.ac.jp"
0 issue "secomtrust.net" 0 issuewild ";" 0 issuemail "secomtrust.net" 0 iodef "mailto:noc@kyokyo-u.ac.jp"
$ dig +short CAA kyokyo-u.ac.jp
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.
ns.kyokyo-u.ac.jp dns-x.sinet.ad.jp
$ dig +short NS kyokyo-u.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 rules1 observed gaps
- PCI DSS v4.0Not applicable
- NIS2 / vendor due diligence2 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 | kyokyo-u.ac.jp | — |
| AAAA | kyokyo-u.ac.jp | — |
| MX | kyokyo-u.ac.jp | 10 mailrelay2.kyokyo-u.ac.jp | 10 mailrelay1.kyokyo-u.ac.jp |
| NS | kyokyo-u.ac.jp | ns.kyokyo-u.ac.jp | dns-x.sinet.ad.jp |
| TXT | kyokyo-u.ac.jp | v=spf1 include:spf.kyokyo-u.ac.jp include:_spf.google.com include:spf.protection.outlook.com include:spf.haihaimail.jp -all | google-site-verification=IN7RJOmh03D1Ehf1rDhSz_1VgeTA1jUd3y_mOIniG5Y | MS=D075BA0FFA55FD6902AD4F319DFD036A35910B75 |
| TXT | _dmarc.kyokyo-u.ac.jp | — |
| CAA | kyokyo-u.ac.jp | 0 issue "secomtrust.net" | 0 issuewild ";" | 0 issuemail "secomtrust.net" | 0 iodef "mailto:noc@kyokyo-u.ac.jp" |
| DS | kyokyo-u.ac.jp | — |