amayakids.com security report

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

92risk

Critical

Exposed services or known CVEs need attention now.

1Critical

12High

28Medium

5Low

2Info

Collected 2 hours ago6.0sfrom cache

Certificate Transparency199
DNS resolution21
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs73
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis48

noteFound 199 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 19 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 116.203.137.198 (m8p.prometheus.amayakids.com), which advertise openssh 7.6p1, nginx 1.14.0. 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 CVE-2018-16845 CVE-2018-16844 CVE-2018-16843
What to do
Confirm the running versions on 116.203.137.198 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: 116.203.137.198
Shodan matched these CVEs against the service banners it saw on 167.235.53.206 (prometheus.amayakids.com), which advertise rabbitmq 3.6.10, openssh 7.6p1, grafana 12.0.2%2bsecurity. 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-46118 CVE-2022-31008 CVE-2021-32719 CVE-2021-32718 CVE-2021-22116
What to do
Confirm the running versions on 167.235.53.206 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2023-46118 ↗CVE-2022-31008 ↗CVE-2021-32719 ↗CVE-2021-32718 ↗CVE-2021-22116 ↗
asset: 167.235.53.206
Shodan matched these CVEs against the service banners it saw on 95.217.7.95 (aso1p.prometheus.amayakids.com), which advertise openssh 8.9p1, nginx 1.18.0. 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
What to do
Confirm the running versions on 95.217.7.95 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 ↗
asset: 95.217.7.95
Shodan matched these CVEs against the service banners it saw on 65.21.248.81 (rsp.prometheus.amayakids.com), which advertise openssh 8.9p1, nginx 1.18.0, rabbitmq 3.12.10. 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
What to do
Confirm the running versions on 65.21.248.81 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 ↗
asset: 65.21.248.81
Shodan matched these CVEs against the service banners it saw on 37.27.20.129 (esp.prometheus.amayakids.com), which advertise nginx 1.18.0, jquery 3.5.1, openssh 8.9p1, rabbitmq 3.12.8. 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
What to do
Confirm the running versions on 37.27.20.129 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 ↗
asset: 37.27.20.129
Shodan matched these CVEs against the service banners it saw on 65.108.53.116 (m6pdb.prometheus.amayakids.com), which advertise openssh 8.9p1, nginx 1.18.0. 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
What to do
Confirm the running versions on 65.108.53.116 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 ↗
asset: 65.108.53.116
Shodan matched these CVEs against the service banners it saw on 167.235.151.254 (m9p.prometheus.amayakids.com), which advertise openssh 8.2p1, nginx 1.22.0. 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 167.235.151.254 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: 167.235.151.254
Shodan matched these CVEs against the service banners it saw on 65.108.49.81 (tsp.prometheus.amayakids.com), which advertise clickhouse 23.10.1.1976, openssh 8.9p1, nginx 1.18.0. 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
What to do
Confirm the running versions on 65.108.49.81 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 ↗
asset: 65.108.49.81
Shodan matched these CVEs against the service banners it saw on 65.109.231.32 (auths.prometheus.amayakids.com), which advertise openssh 8.9p1, nginx 1.18.0. 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
What to do
Confirm the running versions on 65.109.231.32 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 ↗
asset: 65.109.231.32
Shodan matched these CVEs against the service banners it saw on 65.109.169.9 (authp.prometheus.amayakids.com), which advertise nginx 1.18.0, openssh 8.9p1. 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
What to do
Confirm the running versions on 65.109.169.9 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 ↗
asset: 65.109.169.9
Shodan matched these CVEs against the service banners it saw on 37.27.28.64 (amayakids.com), which advertise openssh 8.9p1, nginx 1.18.0. 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
What to do
Confirm the running versions on 37.27.28.64 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 ↗
asset: 37.27.28.64
Shodan matched these CVEs against the service banners it saw on 135.181.152.143 (m6p.prometheus.amayakids.com), which advertise nginx 1.18.0. 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
What to do
Confirm the running versions on 135.181.152.143 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 ↗
asset: 135.181.152.143
Nothing tells receiving mail servers which hosts may send as @amayakids.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: amayakids.com
167.235.53.206 (prometheus.amayakids.com) reports rabbitmq 3.6.10, openssh 7.6p1, grafana 12.0.2%2bsecurity. 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: 167.235.53.206
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: 167.235.53.206:22
95.217.7.95 (aso1p.prometheus.amayakids.com) reports openssh 8.9p1, nginx 1.18.0. 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: 95.217.7.95
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: 95.217.7.95:22
65.21.248.81 (rsp.prometheus.amayakids.com) reports openssh 8.9p1, nginx 1.18.0, rabbitmq 3.12.10. 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: 65.21.248.81
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: 65.21.248.81:22
37.27.20.129 (esp.prometheus.amayakids.com) reports nginx 1.18.0, jquery 3.5.1, openssh 8.9p1, rabbitmq 3.12.8. 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.27.20.129
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.27.20.129:22
65.108.53.116 (m6pdb.prometheus.amayakids.com) reports openssh 8.9p1, nginx 1.18.0. 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: 65.108.53.116
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: 65.108.53.116:22
167.235.151.254 (m9p.prometheus.amayakids.com) reports openssh 8.2p1, nginx 1.22.0. 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: 167.235.151.254
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: 167.235.151.254:22
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: 167.235.151.254:4444
65.108.49.81 (tsp.prometheus.amayakids.com) reports clickhouse 23.10.1.1976, openssh 8.9p1, nginx 1.18.0. 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: 65.108.49.81
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: 65.108.49.81:22
65.109.231.32 (auths.prometheus.amayakids.com) reports openssh 8.9p1, nginx 1.18.0. 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: 65.109.231.32
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: 65.109.231.32:22
65.109.169.9 (authp.prometheus.amayakids.com) reports nginx 1.18.0, openssh 8.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: 65.109.169.9
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: 65.109.169.9:22
37.27.28.64 (amayakids.com) reports openssh 8.9p1, nginx 1.18.0. 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.27.28.64
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.27.28.64:22
116.203.137.198 (m8p.prometheus.amayakids.com) reports openssh 7.6p1, nginx 1.14.0. 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: 116.203.137.198
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: 116.203.137.198:22
135.181.152.143 (m6p.prometheus.amayakids.com) reports nginx 1.18.0. 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: 135.181.152.143
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://amayakids.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://amayakids.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://amayakids.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: amayakids.com
grafana.amayakids.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: grafana.amayakids.com
grafana.test.infra.amayakids.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: grafana.test.infra.amayakids.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://amayakids.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://amayakids.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: amayakids.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: amayakids.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: amayakids.com

final https://amayakids.com/status 200time 618msstack cloudflare

–http:// redirects to https://port 80 did not answer
✗Strict-Transport-Security
✗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 1 server
smtp.google.com
✗SPF
no record
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
kira.ns.cloudflare.com sid.ns.cloudflare.com

✓Registered with Regional Network Information Center, JSC dba RU-CENTER14.5 years old
amayakids.com
✓Registration expiry190 days
2027-03-17
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
kira.ns.cloudflare.com sid.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
167.235.53.206 prometheus.amayakids.com +2	2280300040404369567280808888+3	5	direct	—
95.217.7.95 aso1p.prometheus.amayakids.com +2	228044321813102507085009009+3	4	direct	—
65.21.248.81 rsp.prometheus.amayakids.com +1	228044331024369567290909100	4	direct	—
37.27.20.129 esp.prometheus.amayakids.com +2	228044343695672900915672	4	direct	—
65.108.53.116 m6pdb.prometheus.amayakids.com +1	22804439009909091009187	4	direct	—
167.235.151.254 m9p.prometheus.amayakids.com +1	22804444900990909100	2	direct	—
65.108.49.81 tsp.prometheus.amayakids.com +2	2280443218190089092	4	direct	—
65.109.231.32 auths.prometheus.amayakids.com +1	228044390099090	4	direct	—
65.109.169.9 authp.prometheus.amayakids.com +1	228090099209	4	direct	—
37.27.28.64 amayakids.com +2	2280443	4	direct	—
116.203.137.198 m8p.prometheus.amayakids.com +1	22809009	11	direct	—
135.181.152.143 m6p.prometheus.amayakids.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.

amayakids.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames