groupalarm.com security report

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

15risk

Low

Minor observations only.

0Critical

0High

0Medium

18Low

2Info

Collected 6 hours ago22.3sfrom cache

Headers—

unavailable

Certificate Transparency52
DNS resolution50
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs111
Registration
DNS posture2
Email authentication2
Certificate
Security headers
Archived URLs
Analysis20

noteFound 52 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 14 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.
noteSecurity headers 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.
note8 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

104.17.157.243 (img.mail.groupalarm.com) reports bootstrap 5.1.3. 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: 104.17.157.243
104.17.159.243 (img.mail.groupalarm.com) reports bootstrap 5.1.3. 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: 104.17.159.243
104.17.156.243 (img.mail.groupalarm.com) reports bootstrap 5.1.3. 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: 104.17.156.243
104.17.158.243 (img.mail.groupalarm.com) reports bootstrap 5.1.3. 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: 104.17.158.243
104.17.155.243 (img.mail.groupalarm.com) reports bootstrap 5.1.3. 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: 104.17.155.243
test.groupalarm.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: test.groupalarm.com
app-staging.groupalarm.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: app-staging.groupalarm.com
box-staging.groupalarm.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: box-staging.groupalarm.com
sso-staging.groupalarm.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: sso-staging.groupalarm.com
test-staging.groupalarm.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: test-staging.groupalarm.com
matrix-staging.groupalarm.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: matrix-staging.groupalarm.com
cockpit-staging.groupalarm.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: cockpit-staging.groupalarm.com
developer-staging.groupalarm.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: developer-staging.groupalarm.com
messenger-staging.groupalarm.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: messenger-staging.groupalarm.com
matrix-staging-mas.groupalarm.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: matrix-staging-mas.groupalarm.com
monitoring-staging.groupalarm.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: monitoring-staging.groupalarm.com
matrix-staging-sygnal.groupalarm.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: matrix-staging-sygnal.groupalarm.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: groupalarm.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: groupalarm.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: groupalarm.com

✓Receives mail via 2 servers
mxa.eu.mailgun.org mxb.eu.mailgun.org
!SPFends in ~all
v=spf1 include:mailgun.org ~all
✓DMARCp=reject
v=DMARC1; p=reject;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
james.ns.cloudflare.com jule.ns.cloudflare.com

✓Registered with CPS-Datensysteme GmbH22.4 years old
groupalarm.com
✓Registration expiry225 days
2027-04-20
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
james.ns.cloudflare.com jule.ns.cloudflare.com

Address	Ports	Edge	Network
104.26.3.111 groupalarm.com +14	80443205220532082208320862087+5	Cloudflare~	—
172.67.70.154 groupalarm.com +12	80443205220532082208320862087+5	Cloudflare~	—
104.26.2.111 groupalarm.com +14	80443205220532082208320862087+5	Cloudflare~	—
104.17.157.243 img.mail.groupalarm.com +3	80443205220532082208320862087+5	Cloudflare~	—
104.17.159.243 img.mail.groupalarm.com +3	80443205220532082208320862087+5	Cloudflare~	—
104.17.156.243 img.mail.groupalarm.com +2	80443205220532082208320862087+5	Cloudflare~	—
104.17.158.243 img.mail.groupalarm.com +2	80443205220532082208320862087+5	Cloudflare~	—
104.17.155.243 img.mail.groupalarm.com +3	80443205220532082208320862087+5	Cloudflare~	—
172.246.243.65 r.mail.groupalarm.com +1	80443	direct	—
13.35.36.48 status.groupalarm.com +2	80443	direct	—
13.35.36.84 status.groupalarm.com +2	80443	direct	—
34.38.174.199 box-staging.groupalarm.com +1	8883	direct	—

Archived URLs

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

groupalarm.com security report

Low

Findings

Email authentication

DNS

Registration

Hosts

Hostnames