starclinch.com security report

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

79risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

4Medium

4Low

1Info

Collected 3 hours ago20.8sfrom cache

Certificate Transparency36
DNS resolution24
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs53
Registration
DNS posture2
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis12

noteFound 36 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 103.195.185.118 (my.starclinch.com), which advertise exim 4.99.5, openssh 7.4, mysql 5.7.23-23, nginx 1.25.5. 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-2026-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2025-32728 CVE-2025-26465 CVE-2025-23419 ...and 18 more
What to do
Confirm the running versions on 103.195.185.118 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 103.195.185.118
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 103.195.185.118:3306
Shodan matched these CVEs against the service banners it saw on 34.47.241.113 (rms.starclinch.com), which advertise nginx 1.24.0, jquery 3.5.1. 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
What to do
Confirm the running versions on 34.47.241.113 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗
asset: 34.47.241.113
103.195.185.118 (my.starclinch.com) reports exim 4.99.5, openssh 7.4, mysql 5.7.23-23, nginx 1.25.5. 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.195.185.118
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 103.195.185.118:21
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.195.185.118:22
34.47.241.113 (rms.starclinch.com) reports nginx 1.24.0, jquery 3.5.1. 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: 34.47.241.113
beta.starclinch.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: beta.starclinch.com
rms-dev.starclinch.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: rms-dev.starclinch.com
dev-cockpit.starclinch.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: dev-cockpit.starclinch.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: starclinch.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: starclinch.com

final https://starclinch.com/status 200time 522msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains, max-age=31536000; includeSubDomains; preload
✓Content-Security-Policy
frame-ancestors 'self' https://list.starclinch.com http://localhost:3000
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff, nosniff
✓Referrer-Policy
no-referrer-when-downgrade
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 include:sender.zoho-books.in include:_spf.google.com ~all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:v6hinsuj@ag.dmarcian-ap.com;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
dora.ns.cloudflare.com norm.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC11.7 years old
starclinch.com
✓Registration expiry120 days
2027-01-05
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
dora.ns.cloudflare.com norm.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
103.195.185.118 my.starclinch.com +4	2122265380110143443+12	33	direct	—
172.67.145.235 starclinch.com +11	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.89.179 starclinch.com +11	80443205220532082208320862087+5	0	Cloudflare~	—
34.47.241.113 rms.starclinch.com +1	8044315672	2	direct	—
151.101.65.195 url.starclinch.com +101	80443	0	direct	—
151.101.1.195 url.starclinch.com +1	80443	0	direct	—

Archived URLs

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

starclinch.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames