predge.jp security report

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

85risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

4Medium

5Low

2Info

Collected 19 hours ago18.1sfrom cache

Certificate Transparency4
DNS resolution11
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs18
Registration
DNS posture4
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis14

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.

Shodan matched these CVEs against the service banners it saw on 35.72.93.251 (pdf.predge.jp), which advertise http server 2.4.58, openssl 1.0.2k. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-49975 CVE-2026-48913 CVE-2026-45447 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42766 CVE-2026-42536 CVE-2026-42535 CVE-2026-34356 CVE-2026-34355 CVE-2026-34180 CVE-2026-34059 ...and 93 more
What to do
Confirm the running versions on 35.72.93.251 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-48913 ↗CVE-2026-45447 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗
asset: 35.72.93.251
Nothing tells receiving mail servers which hosts may send as @predge.jp, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: predge.jp
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.predge.jp TXT "v=DMARC1; p=none; rua=mailto:dmarc@predge.jp"`, review the reports, then move to p=quarantine and p=reject.
asset: predge.jp
35.72.93.251 (pdf.predge.jp) reports http server 2.4.58, openssl 1.0.2k. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 35.72.93.251
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://predge.jp/
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://predge.jp/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://predge.jp/
13.35.238.69 (www.predge.jp) reports bootstrap 5. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 13.35.238.69
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://predge.jp/
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://predge.jp/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://predge.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: predge.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: predge.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: predge.jp

final https://predge.jp/status 200time 362msstack cloudflare · PHP/8.3.27

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

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
✗SPF
no record
✗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
ns-1270.awsdns-30.org ns-1621.awsdns-10.co.uk ns-477.awsdns-59.com ns-937.awsdns-53.net

Address	Ports	CVEs	Edge	Network
13.35.163.97 predge.jp +2	80443	0	direct	—
13.35.163.17 predge.jp +2	80443	0	direct	—
13.35.163.93 predge.jp +2	80443	0	direct	—
13.35.163.87 predge.jp +2	80443	0	direct	—
13.35.238.29 www.predge.jp +2	80443	0	direct	—
13.35.238.123 www.predge.jp +2	80443	0	direct	—
13.35.238.88 www.predge.jp +15	80443	0	direct	—
13.35.238.69 www.predge.jp +2	80443	0	direct	—
18.181.99.177 pdf.predge.jp +1	443	0	direct	—
35.72.93.251 pdf.predge.jp +2	443	108	direct	—
18.176.123.231 pdf.predge.jp	none known	0	direct	—

Archived URLs

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

predge.jp security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames