Skip to security report
Domain security and threat intelligence
s.teams-rd.com favicon

s.teams-rd.com

“Sign In”

Registrar
Registrar of Domain Na…
Resolved IP
172.67.133.195
Registered
Aug 26, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 4/92 Automated brand label: Steam
Oct 19, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 4 / 92 6 sources

VirusTotal

4 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
4 / 92
Page captures
3

PhishDestroy threat report

Overview

s.teams-rd.com was first detected by PhishDestroy on 2026-10-19 and immediately added to its blocklist. The site’s exact purpose is unclear, but its inclusion in a dedicated anti-fraud blocklist indicates elevated risk. PhishDestroy has not yet classified the specific threat associated with this domain, and its status remains marked as unknown.

How the scam works

Domains like s.teams-rd.com are typically used to mimic legitimate platforms or services, tricking visitors into entering sensitive information, downloading malicious files, or authorizing wallet connections under false pretenses. Visitors risk credential theft, financial loss, or unauthorized access to digital assets if the site prompts for actions like logging in or approving transactions. Without confirmed branding or kit details, the precise mechanism cannot be specified, but the risk aligns with phishing or impersonation tactics.

Evidence

VirusTotal returned 4 detections out of 92 engines on 2026-10-19, including signatures from alphaMountain.ai, CRDF, ESET, and Webroot. PhishDestroy added the domain to its blocklist on the same day. No additional third-party blocklists or reputation services have flagged the domain at this time.

Infrastructure

The domain resolves to IP address 104.21.14.119, hosted on Cloudflare’s network. No registration date, registrar, TLS issuer, or further infrastructure details are available.

What to do

If you visited s.teams-rd.com, do not enter any credentials, download files, or connect wallets. Check accounts for unusual activity and change passwords elsewhere if the same credentials were reused. For defenders, block traffic to 104.21.14.119 and the domain at the network perimeter.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Steam report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Registrar of Domain Na… UA(UA)
Registration (base domain)teams-rd.com · Created Aug 26, 2026 (54d · New) — Expires Aug 26, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
DOM Analysisanalyzed Oct 19, 2026score 71/1002 brand signals
Submitted URLhttp://s.teams-rd.com/p/fjbd-cbch/wevgmaqp
Favicon Hash
Case ID
Observed page title
Sign In
Automated brand references
Steam Valve
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 35 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.133.195
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • iris.ns.cloudflare.com
  • sage.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-08-26 14:47:46
Valid until
2026-11-24 15:44:00
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-19 04:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbf9492870ff9c9ae59541f4bd0ac9da744bb27c1687c36c8602a3489c69af232
Certificate names · 1 SANs
  • teams-rd.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 10:03:57 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-19 10:03:57 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-19 10:03:57 UTC last content: 2026-10-19 10:03:57 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
CRDF
ESET
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of s.teams-rd.com · checked Oct 19, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.17s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://s.teams-rd.com/p/fjbd-cbch/wevgmaqp
Final URL: https://s.teams-rd.com/p/fjbd-cbch/wevgmaqp
Sign In
Response
HTTP 200
HTML body
77.1 KB
Compressed
14.7 KB
Links
32 internal · 92 external
Detected technologies
jquerycloudflarereact
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Content-Security-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Sign In
Twitter card: summary_large_image
Saved response-header values · 16
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4cbf98a4a2bd212-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
upgrade-insecure-requests
Content-Type
text/html; charset=UTF-8
Date
Mon, 19 Oct 2026 01:22:58 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=a%2F3YDM2Q3wDYgSEFVnLiTFbHwjNRNO4bPCFLESOAQL3Y2KewQutGVdIvaHyVAb%2Friu9yTGRwy1LQElMyhViG1bxpByGHRsInBNIcuwMcOl8rX6v4AurDjIPPT8lrHWW%2FCw%3D%3D"
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Browser
Sign In
Crawler
Сайт s.teams-se.com припаркован на 4host.pro
s.teams-rd.com
Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261019-2D276B

    abuse@reg.ru
  2. URLScan

    Page captured

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. VirusTotal

    4/92 engine detections

    View source
  5. Added to PhishDestroy

    s.teams-rd.com

    View source

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261019-2D276B Recipient: abuse@reg.ru
PDF notice generated Notice text archived (324 chars)
Abuse notice text as sent to the provider
Registrar: REG.RU (Russia)
Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed
Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including s.teams-rd.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/s.teams-rd.com"
  title="PhishDestroy threat report for s.teams-rd.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>