naganoblog.jp security report

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

27risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

1Low

2Info

Collected 1 hour ago81.2sfrom cache

Headers—

unavailable

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.
noteNo registration data: RDAP has no record at this level.
noteSecurity headers did not complete (20). Results below are partial.

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.naganoblog.jp TXT "v=DMARC1; p=none; rua=mailto:dmarc@naganoblog.jp"`, review the reports, then move to p=quarantine and p=reject.
asset: naganoblog.jp
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: naganoblog.jp
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: naganoblog.jp
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: naganoblog.jp

Address	Ports	CVEs	Edge	Network
106.184.98.198 naganoblog.jp +2	80443	0	direct	—

Archived URLs

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