qtx.com security report

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

60risk

Elevated

Several issues worth triaging this week.

0Critical

2High

2Medium

4Low

2Info

Collected 8 hours ago30.7sfrom cache

Certificate Transparency12
DNS resolution30
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs31
Registration
DNS posture2
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis10

noteFound 13 addresses; enriching the first 12.
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.

Nothing tells receiving mail servers which hosts may send as @qtx.com, 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: qtx.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.qtx.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@qtx.com"`, review the reports, then move to p=quarantine and p=reject.
asset: qtx.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.qtx.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.qtx.com/
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.qtx.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.qtx.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.qtx.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: qtx.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: qtx.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: qtx.com

final https://www.qtx.com/status 200time 3456msstack cloudflare

✓http:// redirects to https://
!Strict-Transport-Security
max-age=15724800; includeSubDomains
✗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 2 servers
mxbiz1.qq.com mxbiz2.qq.com
✗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
✓2 nameservers
cellist.dnspod.net twenty.dnspod.net

✓Registered with GoDaddy.com, LLC31.1 years old
qtx.com
✓Registration expiry1073 days
2029-08-16
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns3.dnsv2.com ns4.dnsv2.com

Address	Ports	Edge	Network
163.181.201.185 www.qtx.com +3	804438431935	direct	—
110.42.100.240 qtx.com +2	40359527952951362	direct	—
163.181.201.184 www.qtx.com +3	804431935	direct	—
163.181.201.186 www.qtx.com +3	804431935	direct	—
163.181.201.183 www.qtx.com +3	804431935	direct	—
163.181.201.188 www.qtx.com +3	804431935	direct	—
110.42.100.32 qtx.com +2	80443675	direct	—
163.181.201.187 www.qtx.com +2	80443	direct	—
163.181.201.189 www.qtx.com +2	80443	direct	—
163.181.201.182 www.qtx.com +2	80443	direct	—
110.42.100.94 qtx.com +2	80443	direct	—
43.240.156.51 qtx.com +2	none known	direct	—

Archived URLs

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

qtx.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames