sidrachain.store returned HTTP status 502 in an HTTP check dated 2026-10-01, a recorded server response rather than a statement about the site's content. The domain was first observed on 2026-09-12, the same date recorded for its registration and its PageSpeed performance score of 93.
Recorded Evidence
The PhishDestroy internal listing records sidrachain.store as listed, and VirusTotal recorded 6 detections across 89 scanners in a check dated 2026-09-22. The registrar is Global Domain Group LLC, and the SSL certificate was issued by Let's Encrypt / YR1 in a scan dated 2026-09-12. The IP address 163.61.188.7 is recorded in the United States under MIT, and the PageSpeed check dated 2026-09-12 returned a performance score of 93.
Interpretation
The PhishDestroy listing and the VirusTotal detection count are separate source records with different dates, so they describe distinct observations rather than one combined finding. The HTTP 502 response dated 2026-10-01 describes only that recorded request, and the PageSpeed score dated 2026-09-12 describes a separate measurement. Because the first observation, registration, SSL scan and PageSpeed check share the date 2026-09-12, that calendar overlap alone does not establish simultaneous measurement.
Recommended Actions
Preserve the PhishDestroy listing record and the VirusTotal result for sidrachain.store as separate source records for later comparison. Compare the HTTP response record against the PageSpeed record in separate reviews, since each captures a different kind of observation. Retain the first-observed record alongside these sources so future checks can be compared against the earliest dated entry.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/sidrachainStored page reference
IoC extraction recorded 2026-09-13 04:00:11 UTC
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='sidrachain.store', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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 DetectedSep 12, 2026
DOM Analysisanalyzed Sep 12, 2026score 78/1003 brand signals
IoC Extractionscanned Sep 13, 20260 wallet · 1 Telegram IoC
Submitted URLhttps://sidrachain.store/
Favicon Hash
Case ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:32:43 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-26 10:15:46 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-26 10:15:46 UTC → 2026-09-30 16:14:55 UTC · 101.99hmidpoint estimate ≈ 2026-09-28 13:15:20 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.
Google PageSpeed Insights — mobile performance audit of sidrachain.store· checked Sep 12, 2026
93
Good
Performance
FCP
2.35s
First Contentful Paint
LCP
2.82s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.35s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-26 22:15:15 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-12 14:11:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 163.61.188.7.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
sidrachain.store 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.
Sep 27, 2026
Time to First Unavailability
344 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
5 evidence signal groups linked1 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 · sidrachain.store
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.
Content matches2
Same favicon hash or the same page title as this host.
