VirusTotal
17 / 90
“WhatsApp”
meranova.top — Контент недоступен. Олицетворение бренда: WhatsApp; Тип мошенничества: Impersonation. Сводка доказательств: VirusTotal 17/90 (alphaMountain.ai, Certego, CRDF, CSIS Security Group, CyRadar); URLQuery 5 alerts; URLScan malicious verdict; Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 100/100. Регистратор: Gname.
Подробный анализ PhishDestroy AI ниже оставлен на английском, чтобы сохранить исходную криминалистическую запись.
17 / 90
5 threat-system alerts
Сообщитьprovider verdict: malicious
Сообщитьmalicious
СообщитьDBL_PHISH
4 community references
Сообщитьсохраненный отчет
Сообщить 80/100
СообщитьChecked; no threat flag recorded
Сообщить| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | meranova.top |
malicious | Sinkholed |
| OpenDNS | meranova.top |
phishing | Phishing Block |
| DigiCert UltraDNS | meranova.top |
malicious | Sinkholed |
| DNS4EU | meranova.top |
malicious | Sinkholed |
| Quad9 DNS | meranova.top |
malicious | Sinkholed |
Stored evidence for meranova.top: VirusTotal recorded 17 detections among 90 scanners on 2026-09-06. 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 meranova.top. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 17 detections among 90 scanners in the stored snapshot dated 2026-09-06. 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-06 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.
OpenPhish are recorded as named external blocklist observations for meranova.top in the snapshot dated 2026-09-05. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains meranova.top 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.
The record first observed meranova.top on 2026-09-05. The OpenPhish blocklist snapshot is dated 2026-09-05 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-04. A URLScan reference was stored on 2026-09-05 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.
The source stores 43.164.2.217 as the observed address in this record. The registration date for meranova.top is recorded as 2026-09-04. The SSL issuer is recorded as Let's Encrypt / YE2 in the snapshot dated 2026-09-05. 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.
The meranova.top record states that VirusTotal recorded 17 detections among 90 scanners on 2026-09-06. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-05. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 43.164.2.217. The supported conclusion is bounded to the exact stored observations for meranova.top. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to meranova.top during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain meranova.top 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 meranova.top. The stored record does not justify extending that rule to 43.164.2.217 or to other infrastructure records.
Сохраненные данные сравнения данных сканера и браузера для данного хоста, а также проверка отпечатков в режиме реального времени для систем распределения трафика типа «Кейтаро».
Примечание к сканированию: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='meranova.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
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.
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.
a.share-dns.coma9.share-dns.comb.share-dns.netb9.share-dns.netLocation describes the IP network.
7dd6a2facc0cb83174ec5128257b7ac6aad5f6db663f219ded5a1a3ce443e9caSaved 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 meranova.top · checked Sep 5, 2026
43.164.2.217. 16 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-20260905-D6F887 Recipient: abuse@tencent.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
Если вы ввели учетные данные, личную или платежную информацию или загрузили файл с этого домена, примите немедленные меры. Ниже приведены ресурсы, которые помогут вам сообщить об инциденте и защитить себя.
Выберите свою страну, чтобы получить официальные контакты по киберпреступности или создать проект жалобы →.
Template-based draft · optional AI wording assistance requires separate consent
Анализ угроз с использованием сохраненного черного списка, WHOIS, DNS и общедоступных доказательств сканирования.
Сканировать сейчасДобавляйте подозрительные домены в нашу базу данных угроз — защищайте сообщество
СообщитьНедавние сообщения о фишинге и наблюдаемые изменения доступности
ОтслеживатьОтслеживайте актуальные угрозы или оспорьте эту запись, если считаете, что это ложное срабатывание