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@beget.com.
The latest stored availability evidence still shows the domain reachable; 27 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.
Stored evidence for lylib.fun: VirusTotal recorded 11 detections among 89 scanners on 2026-09-24. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for lylib.fun. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 11 detections among 89 scanners in the stored snapshot dated 2026-09-24. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-24 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish are recorded as named external blocklist observations for lylib.fun in the snapshot dated 2026-09-29. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains lylib.fun as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed lylib.fun on 2026-09-14. The OpenPhish blocklist snapshot is dated 2026-09-29 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for lylib.fun on 2026-09-29. The HTTP status 200 dated 2026-09-29 records a single response for later comparison. The registration date is separately recorded as 2026-08-30. A URLScan reference was stored on 2026-09-16 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For lylib.fun, the registrar field records Beget LLC; this is kept as an exact source value. The source stores 144.31.25.157 as the observed address in this record. The registration date for lylib.fun is recorded as 2026-08-30. The SSL issuer is recorded as Let's Encrypt / YE1 in the snapshot dated 2026-09-14. The stored ASN observation records 210457 and Kyonix Networks Limited in this record. The observed server header is recorded as nginx/1.24.0 (Ubuntu) in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The lylib.fun record states that VirusTotal recorded 11 detections among 89 scanners on 2026-09-24. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-29. PhishDestroy remains a separate publisher catalogue entry in the stored record. For lylib.fun, the registrar field records Beget LLC; this remains separate from the other source fields. The observed address field in this record contains 144.31.25.157. The supported conclusion is bounded to the exact stored observations for lylib.fun. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to lylib.fun during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain lylib.fun as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to lylib.fun. The stored record does not justify extending that rule to 144.31.25.157 or to other infrastructure records.
Extracted from stored page analysis
Observed indicators
0 wallet · 4 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年10月9日score 98/1003 brand signals
IoC Extractionscanned 2026年9月15日0 wallet · 4 Telegram IoCs
Submitted URLhttp://lylib.fun/
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 fingerprint870fc54e1f561ac8e12d4b3ad1f68b9179321edc823df0a93e8dfffdc5bee694Certificate names · 1 SANs
www.lylib.fun
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:20:50 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:20:50 UTClast content: 2026-10-11 10:20:50 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.
使用技術 · 4 identified
U
Ubuntu
Operating systems
Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.
Google PageSpeed Insights — mobile performance audit of lylib.fun· checked Sep 14, 2026
75
Needs Work
Performance
FCP
1.71s
First Contentful Paint
LCP
5.35s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.17s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-09-14 14:08:10 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 144.31.25.157.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
13 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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 (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.
