scienceworldreport.com security report

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

52risk

Elevated

Several issues worth triaging this week.

0Critical

1High

3Medium

4Low

2Info

Collected 20 hours ago4.9sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture4
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis10

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.

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

final https://www.scienceworldreport.com/status 200time 646msstack cloudflare · PHP/7.4.33

✓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 3 servers
mx.zoho.com mx2.zoho.com mx3.zoho.com
!SPFends in ~all
v=spf1 include:zohomail.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
ns-cloud-e1.googledomains.com ns-cloud-e2.googledomains.com ns-cloud-e3.googledomains.com ns-cloud-e4.googledomains.com

✓Registered with TLDS L.L.C. d/b/a SRSPlus14.6 years old
scienceworldreport.com
✓Registration expiry140 days
2027-01-24
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-cloud-e1.googledomains.com ns-cloud-e2.googledomains.com ns-cloud-e3.googledomains.com ns-cloud-e4.googledomains.com

Address	Ports	CVEs	Edge	Network
34.111.185.81 scienceworldreport.com +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.

scienceworldreport.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames