The domain google.jl.cn was first observed on 2026-10-07 and on that date was recorded by Phishunt as appearing on its external blocklist. Internal records also show that google.jl.cn was listed by phishdestroy, adding another point of reference for its status.
Recorded Evidence
Phishunt included google.jl.cn on its blocklist as of 2026-10-07. Internal phishdestroy records listed google.jl.cn on the same date. The domain was initially observed on 2026-10-07, establishing a timeline for these findings.
Interpretation
The presence of google.jl.cn on both the Phishunt blocklist and the internal phishdestroy listing provides multiple sources documenting its status. The matching observation dates allow for direct comparison of external and internal records, offering a consistent basis for further review.
Recommended Actions
For google.jl.cn, it is recommended to preserve both the Phishunt blocklist entry and the internal phishdestroy listing. These records should be referenced and compared for any subsequent evaluation or investigation of the domain's status.
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:07:55 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:07:55 UTClast content: 2026-10-11 10:07:55 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.
Status Check2026-10-07 17:39:19 UTC
Telemetry event observed.
Threat First Observed2026-10-07 17:06:48 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 38.95.75.43.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
