aarome.org security report

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

78risk

Critical

Exposed services or known CVEs need attention now.

1Critical

3High

5Medium

5Low

2Info

Collected 15 hours ago53.7sfrom cache

Domain—

unavailable

Certificate Transparency22
DNS resolution32
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs71
Registration
DNS posture3
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis16

noteFound 22 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.
noteRegistration did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.
note4 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 54.83.63.20 (aarome.org), which advertise http server 2.4.52. 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-49975 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42536 CVE-2026-42535 CVE-2026-34356 CVE-2026-34355 CVE-2026-34059 CVE-2026-34032 CVE-2026-33857 CVE-2026-33523 CVE-2026-33007 ...and 61 more
What to do
Confirm the running versions on 54.83.63.20 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗CVE-2026-44119 ↗
asset: 54.83.63.20
Shodan matched these CVEs against the service banners it saw on 97.107.135.178 (link.aarome.org), which advertise exim 4.99.4. 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-66141 CVE-2026-66140
What to do
Confirm the running versions on 97.107.135.178 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 97.107.135.178
Shodan matched these CVEs against the service banners it saw on 185.3.93.228 (link.aarome.org), which advertise exim 4.99.4. 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-66141 CVE-2026-66140
What to do
Confirm the running versions on 185.3.93.228 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 185.3.93.228
Shodan matched these CVEs against the service banners it saw on 170.187.131.209 (link.aarome.org), which advertise exim 4.99.4. 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-66141 CVE-2026-66140
What to do
Confirm the running versions on 170.187.131.209 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 170.187.131.209
97.107.135.178 (link.aarome.org) reports exim 4.99.4. 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: 97.107.135.178
185.3.93.228 (link.aarome.org) reports exim 4.99.4. 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: 185.3.93.228
170.187.131.209 (link.aarome.org) reports exim 4.99.4. 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: 170.187.131.209
54.83.63.20 (aarome.org) reports http server 2.4.52. 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: 54.83.63.20
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://aarome.org/
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 97.107.135.178:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.3.93.228:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 170.187.131.209:25
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://aarome.org/
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: aarome.org
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: aarome.org
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: aarome.org

final https://aarome.org/status 200time 805msstack cloudflare · Drupal 10 (https://www.drupal.org)

–http:// redirects to https://port 80 did not answer
✗Strict-Transport-Security
✓Content-Security-Policy
font-src 'self' data: https://themes.googleusercontent.com; img-src 'self' data: https://www.google-analytics.com https://www.googletagmanager.com; object-src '…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 2 servers
mxe1.archivioemail.it mxe2.archivioemail.it
✓SPFends in -all
v=spf1 ip4:95.110.249.229 include:_spf.google.com a:smtp.areasrl.com a:aarome.bywatersolutions.com include:spf.mandrillapp.com include:sendgrid.net include:amazonses.com include:spf.protection.outlook.com include:outboundmail.blackbaud.net include:aspmx.pardot.com include:_spf.salesforce.com include:spf1.formassembly.com -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; sp=quarantine; pct=100;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns1.rrpproxy.net ns2.rrpproxy.net ns3.rrpproxy.net

Address	Ports	CVEs	Edge	Network
104.18.124.73 give.aarome.org +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.18.197.95 give.aarome.org +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.18.1.36 library.aarome.org +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.18.0.36 library.aarome.org +3	80443205220532082208320862087+5	0	Cloudflare~	—
97.107.135.178 link.aarome.org +4	258044310256	2	direct	—
185.3.93.228 link.aarome.org +3	2580443	2	direct	—
170.187.131.209 link.aarome.org +4	2580443	2	direct	—
54.83.63.20 aarome.org +3	80443	76	direct	—
185.255.186.51 janet.aarome.org +2	80443	0	direct	—
13.215.239.219 casam.aarome.org +5	80443	0	direct	—
52.74.6.109 casam.aarome.org +4	80443	0	direct	—
80.211.68.172 dhc.aarome.org +7	443	0	direct	—

Archived URLs

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

aarome.org security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames