On 2026-10-01, tether-gold.lol returned an HTTP 502 status code, indicating a server-side error at that time. The domain was also listed internally by PhishDestroy, suggesting it was catalogued for further review.
Recorded Evidence
VirusTotal scanned tether-gold.lol on 2026-09-14 and reported 4 detections out of 89 total scanners. OTX recorded 4 pulses for the domain on 2026-09-14. The domain was first observed on 2026-09-03 and checked by PhishDestroy's internal listing system. The registrar for tether-gold.lol is Spaceship, Inc.
Interpretation
The evidence from VirusTotal, OTX, and PhishDestroy provides a multi-faceted view of tether-gold.lol's profile, with each source offering distinct data points. The HTTP 502 response on 2026-10-01 highlights a technical issue, while the security scans and internal listing indicate ongoing monitoring from different platforms. The chronology of observations allows for comparison of the domain’s status across several dates and systems.
Recommended Actions
To further assess tether-gold.lol, review and preserve the VirusTotal scan results, OTX pulse records, and PhishDestroy internal listing. Comparing these source records will help clarify the domain’s profile and inform any subsequent investigation or monitoring actions. Maintain documentation of the HTTP response code for technical reference and future checks. Preserve all dated evidence for ongoing analysis and periodic review.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='tether-gold.lol', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
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 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:15:45 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-03 17:28:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-03 17:28:07 UTC → 2026-09-30 16:14:55 UTC · 646.78hmidpoint estimate ≈ 2026-09-17 04:51:31 UTC · precision 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: 4 detections
Gridinsoft
LevelBlue
PhishFort
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-09-14 10:00:16 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-14 08:33:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 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.
已捕获威胁
tether-gold.lol 已检测到并排入队，待进行全面分析
2026年9月3日
Cloudflare Radar Report
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.
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)
