aksesbelajar.com is referenced in a PhishDestroy internal listing recorded on 2026-10-11, and its registration with CV. Rumahweb Indonesia was completed on 2026-03-04. OTX also recorded activity for the domain on the same date, providing additional context for its security profile.
Recorded Evidence
PhishDestroy documented an internal listing for aksesbelajar.com on 2026-10-11. OTX measured 31 pulses for the domain on that date. The domain’s registration was completed with CV. Rumahweb Indonesia on 2026-03-04. The SSL certificate for aksesbelajar.com was issued by Let's Encrypt / YR1 and scanned on 2026-10-11.
Interpretation
PhishDestroy contains a record of an internal catalogue listing event for aksesbelajar.com, which measures its inclusion in a proprietary listing. OTX provides a count of pulses, documenting the domain’s presence in community-sourced intelligence records. These sources each capture distinct aspects of the domain’s recorded security context as of their respective dates.
Recommended Actions
For aksesbelajar.com, retain the PhishDestroy internal listing and OTX pulse records as reference points for future analysis. Compare any new security intelligence entries or catalogue listings for the domain against these preserved records to track changes in its documented security context.
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-11 09:50:43 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 09:50:43 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-11 09:50:43 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.198.79.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
7 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.
(ID)
