ABUSE NOTICE · 72H+ 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@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 6 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.
Security Risks Phishing New Domains Phishing Security threats
证据摘要
关键
VirusTotal
14/92
OTX
4 community refs
URLScan
Stored capture
Assessment
kavino.site returned an HTTP 200 status on 2026-10-07, confirming a successful response from the domain at that time. The domain was also listed on two external blocklists, MetaMask and SEAL, as of the same date.
Recorded Evidence
VirusTotal recorded 4 detections out of 92 scanners for kavino.site on 2026-10-06. OTX noted 4 pulses on 2026-10-07. The domain was internally listed by Phishdestroy and had a PageSpeed performance score of 78 on 2026-10-07. Registration was completed with NAMECHEAP INC on 2026-09-22, and its SSL certificate, issued by Let's Encrypt / YR2, was scanned on 2026-10-07.
Interpretation
These observations show that kavino.site was monitored by multiple security sources within a close timeframe. The domain's inclusion on MetaMask and SEAL blocklists, along with VirusTotal detections and OTX pulses, reflects attention from several platforms. The recorded performance score and registration details further contribute to understanding its documented activity.
Recommended Actions
For kavino.site, it is important to preserve all source records, including blocklist listings, VirusTotal detection results, and OTX pulse counts. Comparing these records in future reviews will help identify any changes or new observations. Additional monitoring of HTTP responses and performance metrics is recommended for ongoing assessment.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='kavino.site', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
注册信息创建 2026年9月22日 (21d · Very New!)—Expires 2027年9月22日
技术详情Provenance & timestamps
首次发现2026年10月7日
DOM Analysisanalyzed 2026年10月9日score 100/100
Submitted URLhttp://kavino.site/
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 22:38:04 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-07 11:15:54 UTClast content: 2026-10-07 11:15:54 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-07 11:15:54 UTC → 2026-10-08 20:20:32 UTC · 33.08hmidpoint estimate ≈ 2026-10-08 03:48:13 UTC · precision medium · basis bounded
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.
技术 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
MalwareURL
Seclookup
SOCRadar
URLQuery
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of kavino.site· checked Oct 7, 2026
78
Needs Work
Performance
FCP
0.9s
First Contentful Paint
LCP
3.95s
Largest Contentful Paint
CLS
0.062
Cumulative Layout Shift
TBT
300ms
Total Blocking Time
SI
4.74s
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 09:02:37 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 64.29.17.65.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
12 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.
(IS)
