atomicsoda.com security report

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

84risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

4Medium

3Low

2Info

Collected 5 hours ago17.4sfrom cache

Certificate Transparency1
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture4
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis12

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 98.94.16.134 (atomicsoda.com), which advertise jquery 2.1.3, bootstrap 3.3.4, nginx 1.28.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-2020-11023 CVE-2020-11022 CVE-2019-11358 CVE-2019-8331 CVE-2018-20677 CVE-2018-20676 CVE-2018-14042 CVE-2018-14040 CVE-2016-10735 CVE-2015-9251
What to do
Confirm the running versions on 98.94.16.134 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2020-11023 ↗CVE-2020-11022 ↗CVE-2019-11358 ↗CVE-2019-8331 ↗CVE-2018-20677 ↗
asset: 98.94.16.134
Nothing tells receiving mail servers which hosts may send as @atomicsoda.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: atomicsoda.com
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.atomicsoda.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@atomicsoda.com"`, review the reports, then move to p=quarantine and p=reject.
asset: atomicsoda.com
98.94.16.134 (atomicsoda.com) reports jquery 2.1.3, bootstrap 3.3.4, nginx 1.28.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: 98.94.16.134
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://atomicsoda.com/arsenal
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://atomicsoda.com/arsenal
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://atomicsoda.com/arsenal
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://atomicsoda.com/arsenal
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://atomicsoda.com/arsenal
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: atomicsoda.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: atomicsoda.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: atomicsoda.com

final https://atomicsoda.com/arsenalstatus 200time 1166msstack cloudflare

✓http:// redirects to https://
✗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 7 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+3
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1032.awsdns-01.org ns-1999.awsdns-57.co.uk ns-496.awsdns-62.com ns-548.awsdns-04.net

✓Registered with Amazon Registrar, Inc.26.6 years old
atomicsoda.com
✓Registration expiry170 days
2027-02-24
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1032.awsdns-01.org ns-1999.awsdns-57.co.uk ns-496.awsdns-62.com ns-548.awsdns-04.net

Address	Ports	CVEs	Edge	Network
98.94.16.134 atomicsoda.com +2	80443	10	direct	—

Archived URLs

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

atomicsoda.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames