spinbyoxxo.com.mx security report

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

85risk

Critical

Exposed services or known CVEs need attention now.

6Critical

23High

9Medium

24Low

2Info

Collected 11 hours ago11.5sfrom cache

Certificate Transparency75
DNS resolution23
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2271
Registration
DNS posture4
Email authentication2
Certificate
Security headers6
Archived URLs
Analysis64

noteFound 75 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 21 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.
noteNo registration data: RDAP has no record at this level.

An unauthenticated Docker socket is root on the host.
What to do
Restrict 2375/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:2375
Open Elasticsearch is the classic source of mass data leaks.
What to do
Restrict 9200/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:9200
An unauthenticated Docker socket is root on the host.
What to do
Restrict 2375/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:2375
Open Elasticsearch is the classic source of mass data leaks.
What to do
Restrict 9200/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:9200
An unauthenticated Docker socket is root on the host.
What to do
Restrict 2375/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:2375
Open Elasticsearch is the classic source of mass data leaks.
What to do
Restrict 9200/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:9200
Windows RPC exposed publicly is a well-known lateral-movement entry point.
What to do
Restrict 135/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:135
Database engines should sit behind a private network.
What to do
Restrict 1433/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:1433
Database engines should sit behind a private network.
What to do
Restrict 1521/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:1521
Remote Docker control should not be internet-facing.
What to do
Restrict 2376/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:2376
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:3306
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:3389
Kibana often ships with no authentication and reads the whole cluster.
What to do
Restrict 5601/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:5601
VNC frequently runs with weak or absent authentication.
What to do
Restrict 5900/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:5900
Windows RPC exposed publicly is a well-known lateral-movement entry point.
What to do
Restrict 135/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:135
Database engines should sit behind a private network.
What to do
Restrict 1433/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:1433
Database engines should sit behind a private network.
What to do
Restrict 1521/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:1521
Remote Docker control should not be internet-facing.
What to do
Restrict 2376/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:2376
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:3306
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:3389
Kibana often ships with no authentication and reads the whole cluster.
What to do
Restrict 5601/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:5601
VNC frequently runs with weak or absent authentication.
What to do
Restrict 5900/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:5900
Windows RPC exposed publicly is a well-known lateral-movement entry point.
What to do
Restrict 135/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:135
Database engines should sit behind a private network.
What to do
Restrict 1433/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:1433
Database engines should sit behind a private network.
What to do
Restrict 1521/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:1521
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:3306
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:3389
Kibana often ships with no authentication and reads the whole cluster.
What to do
Restrict 5601/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:5601
VNC frequently runs with weak or absent authentication.
What to do
Restrict 5900/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:5900
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:21
Commonly a leftover listener or an implant default port.
What to do
Restrict 4444/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:4444
Time-series data is often exposed without authentication.
What to do
Restrict 8086/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:8086
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:21
Commonly a leftover listener or an implant default port.
What to do
Restrict 4444/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:4444
Time-series data is often exposed without authentication.
What to do
Restrict 8086/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:8086
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:21
Commonly a leftover listener or an implant default port.
What to do
Restrict 4444/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:4444
Time-series data is often exposed without authentication.
What to do
Restrict 8086/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:8086
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.181.190:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.161.190:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 45.223.169.190:25
qa.spinbyoxxo.com.mx 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: qa.spinbyoxxo.com.mx
qa-une.spinbyoxxo.com.mx 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: qa-une.spinbyoxxo.com.mx
qa-web.spinbyoxxo.com.mx 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: qa-web.spinbyoxxo.com.mx
qa.app.spinbyoxxo.com.mx 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: qa.app.spinbyoxxo.com.mx
dev-une.spinbyoxxo.com.mx 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-une.spinbyoxxo.com.mx
dev-web.spinbyoxxo.com.mx 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-web.spinbyoxxo.com.mx
qa.info.spinbyoxxo.com.mx 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: qa.info.spinbyoxxo.com.mx
dev.info.spinbyoxxo.com.mx 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.info.spinbyoxxo.com.mx
qa-status.spinbyoxxo.com.mx 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: qa-status.spinbyoxxo.com.mx
qa.retiro.spinbyoxxo.com.mx 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: qa.retiro.spinbyoxxo.com.mx
dev-status.spinbyoxxo.com.mx 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-status.spinbyoxxo.com.mx
dev.retiro.spinbyoxxo.com.mx 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.retiro.spinbyoxxo.com.mx
dev-p2p.web.spinbyoxxo.com.mx 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-p2p.web.spinbyoxxo.com.mx
staging-une.spinbyoxxo.com.mx 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: staging-une.spinbyoxxo.com.mx
staging-web.spinbyoxxo.com.mx 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: staging-web.spinbyoxxo.com.mx
staging.app.spinbyoxxo.com.mx 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: staging.app.spinbyoxxo.com.mx
wiremock-qa.spinbyoxxo.com.mx 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: wiremock-qa.spinbyoxxo.com.mx
dev-auth.web.spinbyoxxo.com.mx 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-auth.web.spinbyoxxo.com.mx
staging.info.spinbyoxxo.com.mx 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: staging.info.spinbyoxxo.com.mx
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://spinbyoxxo.com.mx/
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: spinbyoxxo.com.mx
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: spinbyoxxo.com.mx
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: spinbyoxxo.com.mx

final https://spinbyoxxo.com.mx/status 200time 2242msstack cloudflare · Next.js

–http:// redirects to https://port 80 did not answer
✓Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
✓Content-Security-Policy
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.prismic.io https://*.google-analytics.com https://*.googletagmanager.com https://*…
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
camera=(), microphone=(), geolocation=(), usb=(), payment=()
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie visid_incap_3014405
Secure · HttpOnly · SameSite=none
✓Cookie nlbi_3014405
Secure · HttpOnly · SameSite=none
!Cookie incap_ses_675_3014405
Secure · no HttpOnly · SameSite=none

✓Receives mail via 1 server
spinbyoxxo-com-mx.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com include:_spf.atlassian.net include:_spf.tp.com -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:seguridad@spinbyoxxo.com.mx; ruf=mailto:seguridad@spinbyoxxo.com.mx; fo=1
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1442.awsdns-52.org ns-1785.awsdns-31.co.uk ns-466.awsdns-58.com ns-940.awsdns-53.net

Address	Ports	Edge	Network
45.223.181.190 spinbyoxxo.com.mx +37	1121254353808182+941	direct	—
45.223.161.190 spinbyoxxo.com.mx +38	1121254353808182+940	direct	—
45.223.169.190 www.spinbyoxxo.com.mx +39	1121254353808283+349	direct	—
3.230.57.29 qa-une.spinbyoxxo.com.mx +2	80443	direct	—
54.172.222.243 qa-une.spinbyoxxo.com.mx +2	80443	direct	—
44.214.171.133 qa.app.spinbyoxxo.com.mx +2	80443	direct	—
34.194.118.80 qa.app.spinbyoxxo.com.mx +2	80443	direct	—
13.35.202.71 qa.info.spinbyoxxo.com.mx +2	80443	direct	—
13.35.202.73 qa.info.spinbyoxxo.com.mx +1	80443	direct	—
13.35.202.75 qa.info.spinbyoxxo.com.mx +3	80443	direct	—
13.35.202.98 qa.info.spinbyoxxo.com.mx +4	80443	direct	—
54.165.202.64 staging-une.spinbyoxxo.com.mx +2	443	direct	—

Archived URLs

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

spinbyoxxo.com.mx security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames