rmcbfmplay.com security report

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

9risk

Low

Minor observations only.

0Critical

0High

0Medium

7Low

2Info

Collected 11 hours ago13.6sfrom cache

Headers—

unavailable

Certificate Transparency24
DNS resolution46
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs24
Registration
DNS posture4
Email authentication2
Certificate
Security headers
Archived URLs
Analysis9

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

staging-bff.rmcbfmplay.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: staging-bff.rmcbfmplay.com
staging-www.rmcbfmplay.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: staging-www.rmcbfmplay.com
testing-bff.rmcbfmplay.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: testing-bff.rmcbfmplay.com
testing-www.rmcbfmplay.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: testing-www.rmcbfmplay.com
cast.staging.rmcbfmplay.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: cast.staging.rmcbfmplay.com
cast.testing.rmcbfmplay.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: cast.testing.rmcbfmplay.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: rmcbfmplay.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: rmcbfmplay.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: rmcbfmplay.com

✓Receives mail via 1 server
rmcbfmplay-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 ip4:77.154.154.200/30 ip4:77.154.156.200/30 ip4:80.125.162.0/24 ip4:80.125.182.0/24 include:spf.protection.outlook.com -all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:lbjclwnd1g@rua.powerdmarc.com; ruf=mailto:lbjclwnd1g@ruf.powerdmarc.com; pct=100; fo=1;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓4 nameservers
ns-1085.awsdns-07.org ns-1895.awsdns-44.co.uk ns-52.awsdns-06.com ns-803.awsdns-36.net

✓Registered with SafeBrands SAS5.6 years old
rmcbfmplay.com
✓Registration expiry143 days
2027-01-28
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1085.awsdns-07.org ns-1895.awsdns-44.co.uk ns-52.awsdns-06.com ns-803.awsdns-36.net

Address	Ports	Edge	Network
52.85.118.31 www.rmcbfmplay.com +3	80443	direct	—
52.85.118.5 www.rmcbfmplay.com +4	80443	direct	—
52.85.118.75 www.rmcbfmplay.com +4	80443	direct	—
52.85.118.39 www.rmcbfmplay.com +4	80443	direct	—
52.85.118.93 staging-www.rmcbfmplay.com +2	80443	direct	—
52.85.118.47 staging-www.rmcbfmplay.com +4	80443	direct	—
52.85.118.80 staging-www.rmcbfmplay.com +2	80443	direct	—
52.85.118.53 staging-www.rmcbfmplay.com +3	80443	direct	—
3.174.255.67 testing-www.rmcbfmplay.com +3	80443	direct	—
3.174.255.2 testing-www.rmcbfmplay.com +5	80443	direct	—
3.174.255.58 testing-www.rmcbfmplay.com +2	80443	direct	—
3.174.255.29 testing-www.rmcbfmplay.com +2	80443	direct	—

Archived URLs

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

rmcbfmplay.com security report

Low

Findings

Email authentication

DNS

Registration

Hosts

Hostnames