The domain licor.club was reported by VirusTotal with 6 detections from 92 scanners on 2026-10-02, highlighting its evaluation by multiple security tools. It is also included in the PhishDestroy internal listing, and achieved a PageSpeed performance score of 99 on 2026-10-07.
Recorded Evidence
VirusTotal recorded 6 detections out of 92 scanners for licor.club on 2026-10-02. On 2026-10-08, the domain appeared in 34 OTX pulses, and it was listed in the PhishDestroy internal catalogue. PageSpeed reported a performance score of 99 on 2026-10-07. The domain was registered through Dynadot Inc on 2026-06-05, and its SSL certificate was issued by Let's Encrypt / YR2 and scanned on 2026-10-08.
Interpretation
These dated records from VirusTotal, OTX, and PhishDestroy provide a multi-source view of licor.club's presence in monitoring and security databases. The domain's inclusion in OTX pulses and the internal PhishDestroy listing indicates it has been noticed by threat intelligence and cataloguing services. The PageSpeed result shows that a performance test was conducted, while the VirusTotal data reflects how the domain was assessed by several security scanners at the time.
Recommended Actions
For licor.club, preserve the VirusTotal, OTX, and PhishDestroy records for future review and comparison. Maintain the PageSpeed and SSL certificate scan results as part of ongoing monitoring. Use these source records to inform any further investigation or tracking of licor.club.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Jun 5, 2026 (124d)—Expires Jun 5, 2027
Technical detailsProvenance & timestamps
First DetectedOct 7, 2026
DOM Analysisanalyzed Oct 8, 2026score 88/100
Submitted URLhttp://licor.club/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
213.239.205.92
Network ASN
AS24940
Organization
Hetzner Online GmbH
Observed location
Falkenstein, DE
Nameservers 4
cardenal.hostilimitado.com
momoto.hostilimitado.com
ns1.licor.club
ns2.licor.club
Mail routing 1 MX record
licor.clubpriority 0
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR2
Valid from
2026-10-05 21:03:05
Valid until
2027-01-03 21:03:04
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-07 22:02:16 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb075989fadbc7a1568bf0b98ad9bcebad85ccc1579fd6422c901efd7d0d52662Certificate names · 2 SANs
licor.club.smt.lat
www.licor.club.smt.lat
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-07 20:37:34 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-07 20:37:34 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.
Technologies · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Bfore.Ai PreCrime
Chong Lua Dao
Forcepoint ThreatSeeker
Gridinsoft
Seclookup
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of licor.club· checked Oct 7, 2026
99
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
2.1s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.06s
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-10-07 20:37:34 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 213.239.205.92.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 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.
5 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · licor.club
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Dynadot6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
