info-toyama.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

56risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

5Low

2Info

Collected 9 hours ago8.2sfrom cache

Certificate Transparency2
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture4
Email authentication1
Certificate
Security headers3
Archived URLs
Analysis12

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.info-toyama.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@info-toyama.com"`, review the reports, then move to p=quarantine and p=reject.
asset: info-toyama.com
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.info-toyama.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.info-toyama.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.info-toyama.com/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: info-toyama.com
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.info-toyama.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.info-toyama.com/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.info-toyama.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: info-toyama.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: info-toyama.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: info-toyama.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: info-toyama.com

final https://www.info-toyama.com/status 200time 1117msstack cloudflare

✓http:// redirects to https://
!Strict-Transport-Security
max-age=86400;
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie XSRF-TOKEN
no Secure · no HttpOnly · SameSite=lax
✗Cookie _session
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
infotoyama-com01b.mail.protection.outlook.com
✓SPFends in -all
v=spf1 +ip4:160.16.6.121 +ip4:160.16.6.122 +ip4:202.231.108.131 +ip4:210.236.247.77 include:_spf.heteml.jp include:spf.protection.outlook.com -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
01.dnsv.jp 02.dnsv.jp 03.dnsv.jp 04.dnsv.jp

✓Registered with GMO Internet Group, Inc. d/b/a Onamae.com17.9 years old
info-toyama.com
!Registration expiry51 days
2026-10-28
✗Transfer lock
none
✓4 nameservers at registry
01.dnsv.jp 02.dnsv.jp 03.dnsv.jp 04.dnsv.jp

Address	Ports	CVEs	Edge	Network
210.236.247.77 info-toyama.com +2	804435001723	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

info-toyama.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames