On 2026-10-01, duplicate-disabled-1065826.invalid returned HTTP status 502 according to the recorded observation. The domain was first observed on 2026-09-15, and its registration date is recorded as 2026-08-30.
Recorded Evidence
The PhishDestroy internal listing records this domain as listed, and OTX recorded four pulses on 2026-09-18. VirusTotal recorded 3 detections across 89 scanners on 2026-09-18, while the SSL certificate was issued by Google Trust Services / WE1 and scanned on 2026-09-16. The registrar is HOSTINGER operations, UAB, and the PageSpeed performance score was 86 on 2026-09-15.
Interpretation
The PhishDestroy listing and the OTX pulses were recorded on different dates, so a reader can compare them only as separate observations rather than a single snapshot. The VirusTotal result and the HTTP status were also captured on separate dates, which limits direct comparison between them. The SSL scan date falls between the first observation and the HTTP check, adding another distinct point in the timeline.
Recommended Actions
Reviewers should retain the dated records for duplicate-disabled-1065826.invalid, including the PhishDestroy listing and the OTX and VirusTotal observations, so later checks can be compared against them. When comparing subsequent observations, note the exact dates of each source rather than treating them as one measurement. Avoid submitting sensitive information while reviewing duplicate-disabled-1065826.invalid until the recorded status is confirmed by a fresh check.
Extracted from stored page analysis
Observed indicators
2 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-1065826.invalid', port=80): Max retries exceeded with url: / (Caused by
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.
Certificate fingerprint4748c7d8803ef62515f49684031f9bd9e5a8330d996e403d632dec0be7efc076Certificate names · 1 SANs
artificialgatointelligence.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:29:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-16 11:01:25 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.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-1065826.invalid· checked Sep 15, 2026
86
Needs Work
Performance
FCP
1.68s
First Contentful Paint
LCP
4.01s
Largest Contentful Paint
CLS
0.027
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.78s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(LT)
