cpolar.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.

0Critical

3High

11Medium

7Low

2Info

Collected 4 hours ago3.5sfrom cache

Certificate Transparency18
DNS resolution43
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs36
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis23

noteFound 14 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.

Shodan matched these CVEs against the service banners it saw on 101.35.158.146 (api.cpolar.com), which advertise nginx 1.15.12, openssh 9.2p1. 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-2025-23419 CVE-2023-44487 CVE-2021-23017 CVE-2021-3618 CVE-2019-20372 CVE-2019-9516 CVE-2019-9513 CVE-2019-9511
What to do
Confirm the running versions on 101.35.158.146 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗CVE-2021-23017 ↗CVE-2021-3618 ↗CVE-2019-20372 ↗
asset: 101.35.158.146
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 61.160.212.231:3306
Shodan matched these CVEs against the service banners it saw on 175.178.195.28 (svip.cpolar.com), which advertise lua-nginx-module 1.25.3.2, php 8.0.30, openresty 1.25.3.2. 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-5458 CVE-2024-3566 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 175.178.195.28 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2024-5458 ↗CVE-2024-3566 ↗CVE-2013-2220 ↗CVE-2007-3205 ↗
asset: 175.178.195.28
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 103.236.57.21:22
101.35.158.146 (api.cpolar.com) reports nginx 1.15.12, openssh 9.2p1. 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: 101.35.158.146
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 101.35.158.146:22
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 61.160.212.231:22
175.178.195.28 (svip.cpolar.com) reports lua-nginx-module 1.25.3.2, php 8.0.30, openresty 1.25.3.2. 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: 175.178.195.28
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.cpolar.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.cpolar.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.cpolar.com/
The record ends in ?all, so a spoofed message is neither passed nor failed and most receivers let it through.
What to do
End the record with -all (or ~all while you validate your senders).
asset: cpolar.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: cpolar.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: cpolar.com
103.236.57.21 (test1.cpolar.com) reports openssh 9.2p1. 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: 103.236.57.21
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 103.236.57.21:25
61.160.212.231 (db.cpolar.com) reports mariadb 10.3.39-MariaDB-0%2bdeb10u2-log, openssh 7.9p1. 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: 61.160.212.231
test.cpolar.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: test.cpolar.com
sandbox.cpolar.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: sandbox.cpolar.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.cpolar.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: cpolar.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: cpolar.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: cpolar.com

final https://www.cpolar.com/status 200time 1143msstack cloudflare · PHP/8.0.30 · WordPress 6.2.11

✓http:// redirects to https://
✗Strict-Transport-Security
✓Content-Security-Policy
default-src * data: 'unsafe-eval' 'unsafe-inline'
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer-when-downgrade
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie acw_tc
no Secure · HttpOnly · no SameSite
✗Cookie cdn_sec_tc
no Secure · HttpOnly · no SameSite

✓Receives mail via 2 servers
mxbiz1.qq.com mxbiz2.qq.com
!SPFends in ?all
v=spf1 include:spf.mail.qq.com include:servers.mcsv.net ?all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:probezy@gmail.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
vip1.alidns.com vip2.alidns.com

✓Registered with Alibaba Cloud Computing (Beijing) Co., Ltd.8.0 years old
cpolar.com
✓Registration expiry1114 days
2029-09-26
✗Transfer lock
none
✓2 nameservers at registry
vip1.alidns.com vip2.alidns.com

Address	Ports	CVEs	Edge	Network
103.236.57.21 test1.cpolar.com +1	222580110143888993	0	direct	—
163.181.201.185 cpolar.com +5	804438431935	0	direct	—
163.181.201.188 cpolar.com +5	804431935	0	direct	—
163.181.201.183 cpolar.com +5	804431935	0	direct	—
163.181.201.184 cpolar.com +5	804431935	0	direct	—
163.181.201.186 cpolar.com +5	804431935	0	direct	—
101.35.158.146 api.cpolar.com +5	2280443	8	direct	—
163.181.201.187 cpolar.com +4	80443	0	direct	—
163.181.201.189 cpolar.com +4	80443	0	direct	—
163.181.201.182 cpolar.com +4	80443	0	direct	—
61.160.212.231 db.cpolar.com	223306	0	direct	—
175.178.195.28 svip.cpolar.com +1	80443	4	direct	—

Archived URLs

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

cpolar.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames