dpxq.com security report

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

59risk

Elevated

Several issues worth triaging this week.

0Critical

2High

2Medium

3Low

1Info

Collected 17 hours ago30.7sfrom cache

Certificate Transparency4
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture2
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis8

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://dpxq.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://dpxq.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.dpxq.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@dpxq.com"`, review the reports, then move to p=quarantine and p=reject.
asset: dpxq.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://dpxq.com/
Nothing tells receiving mail servers which hosts may send as @dpxq.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: dpxq.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://dpxq.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://dpxq.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: dpxq.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: dpxq.com

final http://dpxq.com/status 200time 30136msstack cloudflare · ASP.NET · notepad

✗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

–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
✓2 nameservers
f1g1ns1.dnspod.net f1g1ns2.dnspod.net

✓Registered with Xin Net Technology Corporation22.0 years old
dpxq.com
✓Registration expiry2545 days
2033-08-26
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
f1g1ns1.dnspod.net f1g1ns2.dnspod.net

Address	Ports	CVEs	Edge	Network
120.27.219.118 dpxq.com +3	80	0	direct	—

Archived URLs

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

dpxq.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames