ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hostinger.com.
The latest stored availability evidence still shows the domain reachable; 10 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
longbowcash.site was observed on 2026-10-04 with a record from ScamSniffer listing it externally. The domain was also internally listed by Phishdestroy, indicating multiple sources have noted its presence.
Recorded Evidence
ScamSniffer included longbowcash.site on its external blocklist as of 2026-10-04. OTX referenced the domain in two pulses on 2026-10-05. Phishdestroy internally listed the domain, and its registration was recorded with HOSTINGER operations, UAB on 2026-09-24. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-04.
Interpretation
The domain has been referenced by several independent sources, each providing a unique observation. The blocklist inclusion and OTX pulses indicate that longbowcash.site has attracted attention from monitoring services. The internal listing by Phishdestroy further expands the scope of recorded evidence, showing that the domain has been cataloged across multiple platforms.
Recommended Actions
For longbowcash.site, it is advisable to review the ScamSniffer blocklist entry and OTX pulse records for further details. Preserve the Phishdestroy internal listing and compare it with external blocklist observations to monitor any changes or new developments. These records should be maintained for ongoing review and assessment of the domain’s status.
Extracted from stored page analysis
Observed indicators
5 wallet · 0 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='longbowcash.site', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
注册信息创建 2026年9月24日 (19d · Very New!)—Expires 2027年9月24日
技术详情Provenance & timestamps
首次发现2026年10月4日
DOM Analysisanalyzed 2026年10月9日score 93/1002 brand signals
IoC Extractionscanned 2026年10月4日5 wallet · 0 Telegram IoCs
Submitted URLhttp://longbowcash.site/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
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.
Certificate fingerprint2a0140627d1aa6f419adc71f9aa7dfbc10d208d5e48db0b8411eeb91b5df90f5Certificate names · 1 SANs
www.longbowcash.site
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 22:36:18 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-03 23:17:09 UTCcurrent episode first observed: 2026-10-04 22:25:13 UTCobserved RIP window: 2026-10-03 23:17:09 UTC → 2026-10-04 22:25:13 UTC · 23.13hmidpoint estimate ≈ 2026-10-04 10:51:11 UTC · precision medium · 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: 2 detections
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
卡巴斯基
Netcraft
SOCRadar
Webroot
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.
Threat First Observed2026-10-03 23:17:09 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 84.32.84.39.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
Blocklist hits included with submission:ScamSniffer
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.
