cnjournals.com security report

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

70risk

Elevated

Several issues worth triaging this week.

0Critical

2High

5Medium

4Low

1Info

Collected 12 hours ago34.8sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture0
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis12

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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.

The site could not be loaded over HTTPS and answered only at http://cnjournals.com/. Every visit — including any login or form — travels unencrypted and can be read or rewritten by anyone on the path. Browsers mark the page "Not secure".
What to do
Get a certificate (Let’s Encrypt is free), serve the site on 443, then redirect port 80 to it and add HSTS.
asset: http://cnjournals.com/
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.cnjournals.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@cnjournals.com"`, review the reports, then move to p=quarantine and p=reject.
asset: cnjournals.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: http://cnjournals.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: http://cnjournals.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: http://cnjournals.com/
Nothing tells receiving mail servers which hosts may send as @cnjournals.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: cnjournals.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: cnjournals.com
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: http://cnjournals.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: http://cnjournals.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: http://cnjournals.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: cnjournals.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: cnjournals.com

final http://cnjournals.com/status 200time 30455msstack cloudflare

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

✗Cookie ASP.NET_SessionId
no Secure · HttpOnly · SameSite=lax
✗Cookie safedog-flow-item
no Secure · no HttpOnly · no SameSite

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓0 nameservers

✓Registered with Jiangsu Bangning Science & technology Co. Ltd.15.1 years old
cnjournals.com
✓Registration expiry340 days
2027-08-13
✗Transfer lock
none
✓2 nameservers at registry
dns3.4cun.com dns4.51dns.top

Address	Ports	CVEs	Edge	Network
182.48.114.90 cnjournals.com	80	0	direct	—

Archived URLs

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

cnjournals.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames