belt2008.com was observed with an HTTP status 303 on 2026-10-11, documenting a recorded redirect response at that time. The domain also appeared in the PhishDestroy internal listing, which is a catalogue entry from the publisher's records.
Recorded Evidence
OTX documented 34 pulses for belt2008.com on 2026-10-11, providing intelligence snapshots from that source. URLScan reported a capture as available on the same date. The domain's registration with Internet Domain Service BS Corp. was recorded as occurring on 2018-10-24. The SSL certificate for belt2008.com was issued by Let's Encrypt / YR1 and scanned on 2026-10-11. The observed server header was Apache, and technologies such as Bootstrap, jQuery, and jQuery Migrate were noted.
Interpretation
The HTTP status source contains a direct measurement of the domain's response code, which describes its response at a specific point in time. PhishDestroy provides a listing record, which is a catalogue entry rather than a technical scan. OTX documents pulse counts, representing community-contributed intelligence snapshots, and URLScan offers a capture report for further technical review. These records together provide a broad view of the domain's observed infrastructure and catalogue presence.
Recommended Actions
For belt2008.com, preserve the HTTP status code and OTX pulse records for future comparison and review. Retain the PhishDestroy listing and URLScan capture as reference points for any subsequent assessments. Use these records to monitor changes in observed domain infrastructure and catalogue entries over time.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:00:27 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:27 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 23:28:52 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.93.90.243.
脅威対応 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.
PDF notice generated Notice text archived (846 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (BS):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and BS's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(BS)
