VirusTotal
10 / 91 engine detections
보고서 열기“Index of /”
Security analysis of team-live.online covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
10 / 91 engine detections
보고서 열기2 threat-system alerts
보고서 열기23 community references
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | team-live.online |
malicious | Sinkholed |
| DNS4EU | team-live.online |
malicious | Sinkholed |
PhishDestroy threat report
The domain team-live.online was registered on 20 April 2026 through a popular registrar and is currently hosted on IP address 66.29.148.137, which resolves to a server located in the United States. The authoritative name servers are launch1.spaceship.net and launch2.spaceship.net, both of which are typical of fast‑deployment hosting environments. The server presents a publicly trusted SSL certificate issued by a well‑known certificate authority, confirming that encrypted connections are accepted without warning.
Web requests to the domain return HTTP status code 200 and deliver a plain directory index page titled “Index of /”. The presence of an open directory listing without custom content is a common indicator of a staging site used to host malicious payloads or phishing landing pages. No additional resources or redirects have been observed, but the bare index suggests that the infrastructure is prepared for rapid content changes.
Reputation services rate the domain extremely poorly: Gridinsoft assigns a trust score of 0 out of 100, and AlienVault OTX has recorded the domain in a single threat pulse. VirusTotal analysis shows that 3 out of 95 scanned security vendors flag the domain as malicious, and the domain appears on three independent blocklists. These signals collectively confirm a high likelihood that the site is being used for credential‑harvesting campaigns.
Defenders should treat team-live.online as a confirmed phishing host. Immediate mitigation steps include adding the domain to DNS‑based blocklists, configuring web‑proxy filters to deny outbound connections, and updating endpoint detection rules to alert on any traffic toward the associated IP address. Continuous monitoring of the nameserver entries and the SSL certificate fingerprint is advised, as changes may indicate a shift in hosting strategy or the deployment of new malicious content.
Last checked
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.
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.
launch2.spaceship.netLocation describes the IP network.
38857bde18c6e2a166a3767aeeadea219d91c428debba7c4ece9c44e1f8072bewww.team-live.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.team-live.onlineDomain recordThe original observation time is not recorded for these hostnames.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://team-live.online/cgi-sys/suspendedpage.cgi; server=LiteSpeed
team-live.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
live_content→redirected
http_redirect
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
No threat flag
View source23 community references
View source10/91 engine detections
View sourceteam-live.online
View source커뮤니티 구성원 1명이 신고 · 최초 확인 2026년 4월 20일
Listed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
team-live.online)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.