coinmate.io security report

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

76risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

3Medium

5Low

1Info

Collected 8 hours ago2.6sfrom cache

Certificate Transparency26
DNS resolution42
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs60
Registration
DNS posture2
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis12

noteFound 26 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.
noteNo registration data: RDAP has no record at this level.
note3 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 37.9.175.164 (start.coinmate.io), which advertise openssh 8.9p1, mysql 5.7.10, mariadb 5.5.45-MariaDB-log, mariadb 11.4.12-MariaDB-ubu2204-log. 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-2023-22084 CVE-2023-22028 CVE-2023-22026 CVE-2023-22015 CVE-2023-22007 CVE-2023-21980 CVE-2023-21977 CVE-2022-21617 CVE-2022-21608 CVE-2022-21595 CVE-2022-21592 CVE-2022-21589 CVE-2022-21460 CVE-2022-21454 CVE-2022-21451 ...and 391 more
What to do
Confirm the running versions on 37.9.175.164 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2023-22084 ↗CVE-2023-22028 ↗CVE-2023-22026 ↗CVE-2023-22015 ↗CVE-2023-22007 ↗
asset: 37.9.175.164
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 37.9.175.164:3306
Database engines should sit behind a private network.
What to do
Restrict 5432/tcp to a VPN, bastion, or allow-listed source range.
asset: 37.9.175.164:5432
37.9.175.164 (start.coinmate.io) reports openssh 8.9p1, mysql 5.7.10, mariadb 5.5.45-MariaDB-log, mariadb 11.4.12-MariaDB-ubu2204-log. 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: 37.9.175.164
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 37.9.175.164: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: 37.9.175.164:22
stage.coinmate.io 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: stage.coinmate.io
auth-stage.coinmate.io 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: auth-stage.coinmate.io
docs-stage.coinmate.io 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: docs-stage.coinmate.io
mock-stage.coinmate.io 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: mock-stage.coinmate.io
binance-proxy.stage.coinmate.io 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: binance-proxy.stage.coinmate.io
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: coinmate.io

final https://coinmate.io/enstatus 200time 770msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✓Content-Security-Policy
default-src 'self'; style-src 'self' 'unsafe-inline' surveys-static-prd.survicate-cdn.com fonts.googleapis.com; font-src 'self' data: fonts.gstatic.com surveys-…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
–Permissions-Policyoptional
✓security.txt published

✓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:_spf.google.com ~all
✓DMARCp=quarantine
v=DMARC1; p=quarantine;
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
✓CAA
0 iodef "mailto:abuse@coinmate.io" · 0 issue "amazon.com" · 0 issue "amazonaws.com" · 0 issue "amazontrust.com" · 0 issue "awstrust.com" · 0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "sectigo.com" · 0 issue "ssl.com" · 0 issuewild "amazon.com" · 0 issuewild "amazonaws.com" · 0 issuewild "amazontrust.com" · 0 issuewild "awstrust.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "sectigo.com" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
albert.ns.cloudflare.com alina.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
37.9.175.164 start.coinmate.io +4	2122804433306331033115432+16	406	direct	—
104.26.0.82 coinmate.io +14	80443205320822083208620872096+3	0	Cloudflare~	—
104.26.1.82 coinmate.io +14	80443205320822083208620872096+3	0	Cloudflare~	—
172.67.71.55 coinmate.io +14	80443208220832086208720968080+2	0	Cloudflare~	—
167.235.220.62 status.coinmate.io +3	80443	0	direct	—
172.246.243.65 r.brevo.coinmate.io +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.

coinmate.io security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames