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.
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.
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Valid from
2026-04-18 00:00:00
Valid until
2026-11-02 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-04-20 14:00:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint38857bde18c6e2a166a3767aeeadea219d91c428debba7c4ece9c44e1f8072beCertificate names · 1 SANs
www.team-live.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 22:31:49 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:31:49 UTClast content: 2026-10-13 22:31:49 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.
Last analyzed Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Sophos
威胁响应 Pipeline
发现
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(US)
