Security engines reporting a detection: 8. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Analysis indicates that the domain teams-room.online is actively engaged in phishing activities. The domain was created on July 17, 2026, and is currently registered through NAMECHEAP INC. It resolves to the IP address 162.255.119.135 and is associated with nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. This domain has been flagged on three security blocklists, indicating recognition of its malicious intent. Furthermore, it has been actively blocked by multiple security solutions, including PhishDestroy, MetaMask, and SEAL, which corroborates its classification as a phishing threat. The high-risk status of this domain necessitates immediate attention from cybersecurity defenders. Organizations should implement measures to block access to this domain and educate users about the risks associated with phishing attempts. As of the report date, the domain remains active, and ongoing monitoring is recommended to track any changes in its status or associated infrastructure.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='teams-room.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJul 20, 2026
DOM Analysisanalyzed Jul 20, 2026score 70/100
Submitted URLhttp://teams-room.online/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:12:30 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-22 10:26:56 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-22 10:26:56 UTC → 2026-09-30 16:14:55 UTC · 1,685.80hmidpoint estimate ≈ 2026-08-26 13:20:55 UTC · precision very low · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 1 detection
alphaMountain.ai
BitDefender
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-08-05 22:00:48 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-07-20 11:24:07 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: Kaspersky.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
teams-room.online detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Aug 6, 2026
Time to First Unavailability
394 hours elapsed from detection to the first unavailable observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
3 evidence signal groups linked0 reports recordedContent unavailable
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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · teams-room.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Namecheap6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
