rcbcy.com security report

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

68risk

Elevated

Several issues worth triaging this week.

1Critical

0High

3Medium

4Low

2Info

Collected 7 hours ago9.6sfrom cache

Certificate Transparency40
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs11
Registration
DNS posture3
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis10

noteFound 40 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.

Shodan matched these CVEs against the service banners it saw on 194.156.65.29 (rcbcy.com), which advertise exim 4.93. 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 CVE-2026-48840 CVE-2026-40687 CVE-2026-40686 CVE-2026-40685 CVE-2026-40684 CVE-2025-67896 CVE-2024-39929 CVE-2023-51766 CVE-2023-42119 CVE-2023-42117 CVE-2023-42116 CVE-2023-42115 CVE-2023-42114 ...and 26 more
What to do
Confirm the running versions on 194.156.65.29 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗CVE-2026-48840 ↗CVE-2026-40687 ↗CVE-2026-40686 ↗
asset: 194.156.65.29
194.156.65.29 (rcbcy.com) reports exim 4.93. 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: 194.156.65.29
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://rcbcy.com/en
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: rcbcy.com
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 194.156.65.29:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 213.207.152.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://rcbcy.com/en
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: rcbcy.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: rcbcy.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: rcbcy.com

final https://rcbcy.com/enstatus 200time 4069msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000;
✗Content-Security-Policy
✓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
mail.rcbcy.com mail2.rcbcy.com
✓SPFends in -all
v=spf1 ip4:213.207.152.209 ip4:64.59.223.198 mx -all
!DMARCp=none
v=DMARC1;p=none;pct=100;fo=1;ri=86400;rua=mailto:rcbbnk_rua@dm.easysol.net;ruf=mailto:rcbbnk_ruf@dm.easysol.net
!MTA-STSinbound mail can be downgraded to plaintext

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

✓Registered with pair Networks, Inc. d/b/a pair Domains24.5 years old
rcbcy.com
✓Registration expiry926 days
2029-03-21
✓Transfer lock
client transfer prohibited
✓3 nameservers at registry
ns1.rcbcy.com ns2.rcbcy.com ns3.rcbcy.com

Address	Ports	CVEs	Edge	Network
194.156.65.29 rcbcy.com +2	255380110143443465587+2	41	direct	—
213.207.152.209 mail.rcbcy.com +1	25	0	direct	—

Archived URLs

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

rcbcy.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames