VirusTotal
15 / 91
报告Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Home - KathmanduHealing”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@enom.com.
The latest stored availability evidence still shows the domain reachable; 21 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.
kathmanduhealing.org — 最后已知的活跃状态 (HTTP 200). 诈骗类型:Impersonation. 证据摘要: VirusTotal 15/91 (ADMINUSLabs, alphaMountain.ai, Chong Lua Dao, CyRadar, ESET); URLQuery 2 det.; PhishDestroy score 100/100. 注册商: eNom.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
15 / 91
报告Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
32 community references
报告Community publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
存储的报告
报告 A preserved page image documents what the collector received; a capture is not a safety verdict.
分析完成
报告This is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
报告A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
kathmanduhealing.org returned HTTP status 200 on 2026-10-01, per the recorded HTTP check. The domain was first observed on 2026-09-23, and its registration date is 2007-09-12 with eNom, LLC as registrar.
The HTTP check on 2026-10-01 recorded status 200 for kathmanduhealing.org. VirusTotal, checked on 2026-09-25, reported 15 detections across 91 scanners. OTX, checked on 2026-09-25, listed 32 pulses. The PhishDestroy internal listing was recorded as true, and the SSL certificate was issued by Let's Encrypt / YE2, scanned on 2026-09-23.
The HTTP check and first observation carry different dates, so the status 200 reflects a single dated response rather than continuous availability. VirusTotal and OTX share the same 2026-09-25 check date, which permits direct comparison of those two snapshots, while the SSL scan and PageSpeed score of 73 were captured earlier on 2026-09-23. Readers should weigh each source by its own timestamp when comparing records.
Retain the dated records for kathmanduhealing.org exactly as captured, including the HTTP, VirusTotal, OTX, and PhishDestroy entries. Compare any later observations of kathmanduhealing.org against these timestamps to identify changes over time. During review, avoid submitting sensitive information to the domain until the evidence has been fully examined.
针对该主机的爬虫与浏览器观察记录,以及针对“Keitaro”式流量分配系统的实时指纹检测。
LiteSpeed扫描说明: alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
emily.ns.cloudflare.comstan.ns.cloudflare.commail.kathmanduhealing.orgpriority 10Location describes the IP network.
8b4e85716d39bc5ab68d3737b03159cae5ea256daeb275dfb1eb8755f7390999ftp.kathmanduhealing.orgmail.kathmanduhealing.orgpop.kathmanduhealing.orgsmtp.kathmanduhealing.orgwebmail.kathmanduhealing.orgwww.kathmanduhealing.orgSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of kathmanduhealing.org · checked Sep 23, 2026
193.108.130.22.11 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260923-0205AA Recipient: abuse@enom.com 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.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent