marujiru.com security report

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

83risk

Critical

Exposed services or known CVEs need attention now.

1Critical

0High

8Medium

8Low

2Info

Collected 21 hours ago4.8sfrom cache

Certificate Transparency3
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs7
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis19

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.

Shodan matched these CVEs against the service banners it saw on 202.144.232.212 (marujiru.com), which advertise php 5.3.10. 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-2024-25117 CVE-2024-3566 CVE-2022-31629 CVE-2022-31628 CVE-2022-4900 CVE-2020-11579 CVE-2019-9641 CVE-2019-9639 CVE-2019-9638 CVE-2019-9637 CVE-2019-9024 CVE-2019-9023 CVE-2019-9021 CVE-2019-9020 CVE-2019-6977 ...and 220 more
What to do
Confirm the running versions on 202.144.232.212 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2024-25117 ↗CVE-2024-3566 ↗CVE-2022-31629 ↗CVE-2022-31628 ↗CVE-2022-4900 ↗
asset: 202.144.232.212
202.144.232.212 (marujiru.com) reports php 5.3.10. 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: 202.144.232.212
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://www.marujiru.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.marujiru.com/
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://www.marujiru.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.marujiru.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.marujiru.com/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: marujiru.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: marujiru.com
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 202.144.232.212:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 182.236.95.33:25
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://www.marujiru.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.marujiru.com/
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://www.marujiru.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.marujiru.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.marujiru.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: marujiru.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: marujiru.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: marujiru.com

final https://www.marujiru.com/status 200time 1105msstack cloudflare · PHP/5.3.10

✓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

✗Cookie shiro_cookie_name
no Secure · no HttpOnly · no SameSite
✗Cookie shiro_session
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
m.emailsys.jp
!SPFends in ~all
v=spf1 +ip4:202.144.232.212 +ip4:103.9.92.221 +ip4:182.236.95.31 +ip4:182.236.95.33 ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:dmarc@emailsys.jp; ruf=mailto:dmarc@emailsys.jp
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dns1.mirai-box.com dns4.nnetworks.co.jp

✓Registered with GMO Internet Group, Inc. d/b/a Onamae.com19.3 years old
marujiru.com
✓Registration expiry270 days
2027-06-04
✗Transfer lock
none
✓2 nameservers at registry
dns1.mirai-box.com dns4.nnetworks.co.jp

Address	Ports	CVEs	Edge	Network
202.144.232.212 marujiru.com +4	2580443587	235	direct	—
182.236.95.33 verup.marujiru.com +3	2580443	0	direct	—

Archived URLs

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

marujiru.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames