On 2026-10-11, elecbits.in was observed with an Apache server header and a page titled Electronics Manufacturing and Supply Chain Solutions Elecbits. The domain was also internally listed by PhishDestroy, providing a dated reference for ongoing monitoring.
Recorded Evidence
PhishDestroy recorded an internal listing for elecbits.in on 2026-10-11. OTX documented 34 pulses for this domain on 2026-10-11. URLScan made a report available for elecbits.in on 2026-10-11. The domain was registered with GoDaddy on 2016-08-14, and its SSL certificate was issued by Let's Encrypt / YE1 as of 2026-10-11.
Interpretation
PhishDestroy contains an internal listing for elecbits.in, which serves as a publisher-managed reference for the domain. OTX provides a count of pulses, representing community-sourced intelligence entries for the domain. The URLScan report offers a technical snapshot of the public page, capturing infrastructure details on the recorded date.
Recommended Actions
For elecbits.in, retain the PhishDestroy internal listing and OTX pulse records for future comparison. Use the URLScan report as a reference point for subsequent technical reviews. These records should be preserved to support ongoing assessments or further analysis of the domain.
DOM Analysisanalyzed 2026年10月11日score 71/1004 brand signals
Submitted URLhttp://elecbits.in/
Favicon Hash
ケース ID
ページタイトル
Electronics Manufacturing and Supply Chain Solutions Elecbits
Impersonates
CelerInstagramLinkedInSignal
TLS証明書
Certificate hostname mismatch·
発行者 Let's Encrypt / YE1· stored validity ends in 63 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
65.2.141.200
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Mumbai, IN
Server header
Apache
ネームサーバー 2
ns11.domaincontrol.com
ns12.domaincontrol.com
Mail routing 5 MX records
aspmx.l.google.compriority 1
alt2.aspmx.l.google.compriority 5
alt1.aspmx.l.google.compriority 5
alt3.aspmx.l.google.compriority 10
alt4.aspmx.l.google.compriority 10
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YE1
Valid from
2026-09-14 19:37:56
Valid until
2026-12-13 19:37:55
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdfec705ae1e4a13e7847f2b2ffc94d1e2ead59c434a1de5071afe160374a6f6eCertificate names · 1 SANs
www.elecbits.in
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-11 10:00:14 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:14 UTClast content: 2026-10-11 10:00:14 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.
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.
Threat First Observed2026-10-10 22:59:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 65.2.141.200.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
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.
(IN)
