ridemetro.org security report

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

18risk

Low

Minor observations only.

0Critical

0High

1Medium

14Low

2Info

Collected 13 hours ago31.2sfrom cache

Certificate Transparency229
DNS resolution6
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs6
Registration
DNS posture2
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis17

noteFound 229 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.

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: ridemetro.org
beta.ridemetro.org 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: beta.ridemetro.org
www.beta.ridemetro.org 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: www.beta.ridemetro.org
dev.brightsign.ridemetro.org 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.brightsign.ridemetro.org
api.dev.brightsign.ridemetro.org 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: api.dev.brightsign.ridemetro.org
www.dev.brightsign.ridemetro.org 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: www.dev.brightsign.ridemetro.org
api.dev.brightrsign.ridemetro.org 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: api.dev.brightrsign.ridemetro.org
storage.dev.brightsign.ridemetro.org 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: storage.dev.brightsign.ridemetro.org
handlers.dev.brightsign.ridemetro.org 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: handlers.dev.brightsign.ridemetro.org
webstorage.dev.brightsign.ridemetro.org 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: webstorage.dev.brightsign.ridemetro.org
legacy.ridemetro.org 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: legacy.ridemetro.org
intranet.ridemetro.org 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: intranet.ridemetro.org
www.legacy.ridemetro.org 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: www.legacy.ridemetro.org
www.intranet.ridemetro.org 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: www.intranet.ridemetro.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: ridemetro.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: ridemetro.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: ridemetro.org

final https://www.ridemetro.org/status 200time 5045msstack cloudflare · Sitefinity 15.4.8636.0 DX

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains
✓Content-Security-Policy
default-src 'self' https://collector-29267.us.tvsquared.com; script-src 'self' *.googleapis.com *.gstatic.com www.google.com apis.google.com *.google-analytics.…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer-when-downgrade
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
ridemetro-org.mail.protection.outlook.com
✓SPFends in -all
v=spf1 ip4:74.124.26.51 ip4:206.225.178.10 ip4:67.211.49.21 ip4:74.124.26.187 ip4:192.254.121.248 ip4:216.32.181.234 ip4:184.106.9.250 ip4:162.219.105.64 ip4:162.219.105.65 include:spf.protection.outlook.com include:_spf.psm.knowbe4.com include:_spf.elasticemail.com include:_spf-dc68.sapsf.com -all
!DMARCp=none
v=DMARC1; p=none; pct=100
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns1.pslightwave.com ns2.pslightwave.com

✓Registered with Network Solutions, LLC26.4 years old
ridemetro.org
✓Registration expiry1314 days
2030-04-13
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.pslightwave.com ns2.pslightwave.com

Address	Ports	Edge	Network
52.127.34.96 ridemetro.org +1	80443	direct	—
157.55.174.249 api.ridemetro.org +3	80443	direct	—
20.140.56.69 www.ridemetro.org +4	80443	direct	—
206.225.177.19 legacy.ridemetro.org	none known	direct	—

Archived URLs

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

ridemetro.org security report

Low

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames