Skip to security report
s.teamrz.homes favicon
Domain security and threat intelligence

s.teamrz.homes

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded s.teamrz.homes on 2026-11-22. Stored VirusTotal result: 5/92 engines flagged. Analysis time (as stored): 2026-11-21 19:20 UTC. Retrieved (as stored): 2026-11-22 15:34 UTC. Listed by external blocklists: OpenPhish.

More about the sources
Recorded security signals

Stored VirusTotal result: 5/92 engines flagged. Analysis time (as stored): 2026-11-21 19:20 UTC. Retrieved (as stored): 2026-11-22 15:34 UTC. Listed by external blocklists: OpenPhish. Use caution — do not enter credentials or personal information.

VirusTotal detections: 5/92 Stored blocklist matches: 1 Young domain: 5 days old
Registrar
Eranet International
Resolved IP
104.21.39.192
Registered
2026-11-17
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
Domain age
registered 2026-11-17 according to WHOIS
2026-11-22 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded s.teamrz.homes on 2026-11-22. Stored VirusTotal result: 5/92 engines flagged. Analysis time (as stored): 2026-11-21 19:20 UTC. Retrieved (as stored): 2026-11-22 15:34 UTC. Listed by external blocklists: OpenPhish. Risk: critical (evidence score 80/100). Registrar: Eranet International. Status: Last known active. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
5 / 92
Blocklist matches
1 external + PhishDestroy list
Hosting
104.21.39.192
Registrar
Eranet International
Registered
2026-11-17
Page captures
2

Recorded source summary

s.teamrz.homes is a subdomain of teamrz.homes. PhishDestroy first observed the hostname on Nov 22, 2026. Stored content metadata identifies Steam as the apparent target. Current evidence score: 80/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, OpenPhish, and URLScan. VirusTotal recorded 5 detections among 92 engines: G-Data, Webroot, Fortinet, SOCRadar, alphaMountain.ai on Nov 21, 2026 at 19:20 UTC. OpenPhish listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 15:20 UTC. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to steam and assigned phishing as its category on Nov 22, 2026 at 15:28 UTC.

HTTP 200 was recorded on Nov 22, 2026 at 15:28 UTC. Registration records for the registrable domain teamrz.homes list Eranet International Limited as the registrar and Nov 17, 2026 as the creation date. Registration preceded first observation by 5 days. At collection time, the hostname resolved to 104.21.39.192. The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 2 visual captures from PhishDestroy and Cloudflare Radar; the captures preserve the landing-page appearance. TLS metadata lists YE1 as the certificate issuer with validity through Feb 15, 2027.

The content indicators and 3 positive source findings support the current Steam impersonation and phishing classification. The target field identifies Steam.

Source evidenceVirusTotal 5 / 92 3 sources

VirusTotal

5 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 9 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
5
Denominator
92
Vendors
alphaMountain.ai, Fortinet, G-Data, SOCRadar, Webroot
Observed at
2026-11-21 19:20:26
Checked at
2026-11-22 16:34:55
Fetched at
2026-11-22 15:34:55

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 20 fields

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
39
Download
0
Response time, ms
85

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
139
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    108.162.193.239
    Host
    toby.ns.cloudflare.com
  • IP address
    108.162.192.175
    Host
    jule.ns.cloudflare.com
DNS zone
teamrz.homes

Page quality

Layout shift (CLS)
0
SEO score
100
Speed Index, s
0.75
First Contentful Paint (FCP), s
0.75
Largest Contentful Paint (LCP), s
0.75
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
100
Best practices score
100

Location

IP address
2606:4700:3035::6815:27c0
ASN
13335
Organization
Cloudflare, Inc.
City
San Francisco
Country
US

TLS certificate

Subject alternative names
  • *.teamrz.homes
  • teamrz.homes
Key size, bits
256
Certificate chain
  • teamrz.homes
  • YE1
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE1
Serial
066F787120BEBBB607FD043C6C06B0C9F47D
SHA-256
1e7651fb13be0f633494f0447840874dba4a78f453b217af5bcd4d9697a0cfe7
Subject
teamrz.homes
Valid until
Valid from

DNS records

A
  • 104.21.39.192
  • 172.67.148.88
AAAA
  • 2606:4700:3032::ac43:9458
  • 2606:4700:3035::6815:27c0

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3032::ac43:9458
IP version
6

Redirects

Redirect chain
  • https://s.teamrz.homes

Registration record

Registrar
Eranet International Limited
Registrar IANA ID
1868
Registrar URL
http://www.eranet.com
Registered
Updated
Expires
Status
  • serverTransferProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • jule.ns.cloudflare.com
  • toby.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
Original source fields · JSON
Protective DNS results
Resolvers: 12; Blocked count: 0
Trackers
Requests: 2
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 39; Download: 0; Response ms: 85
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 139; Co2 grams: 0; Cleaner than: 95
DNS server
NS: (IP: 108.162.193.239; Host: toby.ns.cloudflare.com), (IP: 108.162.192.175; Host: jule.ns.cloudflare.com); Zone: teamrz.homes
Quality
Cls: 0; Seo: 100; Si s: 0.75; Fcp s: 0.75; Lcp s: 0.75; Tbt ms: 0; Performance: 100; Accessibility: 100; Best practices: 100
Location
IP: 2606:4700:3035::6815:27c0; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US
SSL
San: *.teamrz.homes, teamrz.homes; Bits: 256; Chain: teamrz.homes, YE1, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE1; Serial: 066F787120BEBBB607FD043C6C06B0C9F47D; SHA256: 1e7651fb13be0f633494f0447840874dba4a78f453b217af5bcd4d9697a0cfe7; Subject: teamrz.homes; Valid to: 2027-02-15T11:38:12Z; Valid from: 2026-11-17T11:38:13Z
DNS records
A: 104.21.39.192, 172.67.148.88; Aaaa: 2606:4700:3032::ac43:9458, 2606:4700:3035::6815:27c0
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3032::ac43:9458; Family: 6
Redirects
Chain: https://s.teamrz.homes
Registration record
Registrar: Eranet International Limited; Registrar iana ID: 1868; Registrar URL: http://www.eranet.com; Created: 2026-11-17T12:33:37Z; Updated: 2026-11-22T12:34:39Z; Expires: 2027-11-17T23:59:59Z; Status: serverTransferProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp; Nameservers: jule.ns.cloudflare.com, toby.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8

Questions about s.teamrz.homes

Is s.teamrz.homes legit?

PhishDestroy rates s.teamrz.homes as critical risk (evidence score 80/100) from the recorded evidence; it was first recorded on 2026-11-22. Stored VirusTotal result: 5/92 engines flagged. Analysis time (as stored): 2026-11-21 19:20 UTC. Retrieved (as stored): 2026-11-22 15:34 UTC. Listed by external blocklists: OpenPhish. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is s.teamrz.homes safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on s.teamrz.homes. A confirmed blockchain transaction cannot be reversed.

What should I do if I used s.teamrz.homes?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matches1 external + PhishDestroy list · OpenPhish · PhishDestroy 1
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Page captures (2)

All capture links and hashes (2)
TLS Certificate
Issued by YE1 · stored validity ends in 84 days

Domain details

Domain
IP Context 104.21.39.192 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Eranet International
Registration (base domain)teamrz.homes · Created 2026-11-17 (5d · Brand New!) — Expires 2027-11-17
HTTP Status200
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttp://s.teamrz.homes/p/jvs-pwq/jmencser
ICANN OVERSIGHT Registration: teamrz.homes

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

Registrable domain behind this subdomain: teamrz.homes. For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.39.192
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • jule.ns.cloudflare.com
  • toby.ns.cloudflare.com

TLS certificate

Issuer
YE1
Valid from
2026-11-17 11:38:13
Valid until
2027-02-15 11:38:12
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1e7651fb13be0f633494f0447840874dba4a78f453b217af5bcd4d9697a0cfe7
Certificate names · 2 SANs
  • *.teamrz.homes
  • teamrz.homes

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

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
G-Data
Webroot
Fortinet
SOCRadar
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of s.teamrz.homes ·

100
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
0.77 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.77 s
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.teamrz.homes/p/jvs-pwq/jmencser
Final URL: https://s.teamrz.homes/p/jvs-pwq/jmencser/
Steam Community :: DUKALIS
Response
HTTP 200
HTML body
147.0 KB
Compressed
15.9 KB
Links
0 internal · 0 external
Detected technologies
reactjquerycloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Sign In
Twitter card: summary
Saved response-header values · 14
Alt-Svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a5e8f842bfb38e2c-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 22 Nov 2026 15:29:27 GMT
Last-Modified
Tue, 03 Nov 2026 10:41:34 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=V8C9Nj0%2FA2y9hpCIBA38rrauMI4bfj1vA43VX6K2IlQEJMdTOfqc5SB4pCjW%2B9gE2AFvoPJA8xIeRF4zqZ8Vd2pV%2Fh2JAvyQOILZwqj8DajgKPcnT%2FKqNRPnYZ9Aw%2B2ZOA%3D
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
accept-encoding

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

Registration & observation details1

Availability observations

Last reachable observation

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

All stored data72
Open complete records

Captured network requests

Network requests: 120 SHA-256 hashes: 119 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 15:30 UTC.

Open this scan on URLScan 01a203de-e035-72fb-a644-f2ce2cad4699 ↗

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. Domain monitor · First collection record

    Reachable

All retained availability observations0

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

No retained observations are recorded.

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    s.teamrz.homes detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Automated brand label: Steam · Forensic Evidence Collected recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+4 d 6 h
  3. Added to PhishDestroy+20 h 8 min
  1. Wayback Machine

    Page archived

    +1 min
  2. Added to PhishDestroy

    s.teamrz.homes

    same minute
  3. URLScan

    Page captured

    +20 h 8 min
  4. VirusTotal

    5/92 engine detections

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

s.teamrz.homes

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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.teamrz.homes)
  • 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

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 →
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.

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.teamrz.homes"
  title="PhishDestroy threat report for s.teamrz.homes"
  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>