verificator[.]cc
Сводка доказательств
Assessment
Stored evidence for verificator.cc: VirusTotal recorded 19 detections among 91 scanners on 2026-08-07. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for verificator.cc. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 19 detections among 91 scanners in the stored snapshot dated 2026-08-07. 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-08-07 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
MetaMask and SEAL are recorded as named external blocklist observations for verificator.cc in the snapshot dated 2026-08-07. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains verificator.cc as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL 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 verificator.cc on 2026-08-07. The MetaMask and SEAL blocklist snapshot is dated 2026-08-07 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for verificator.cc on 2026-08-07. The HTTP status 200 dated 2026-08-07 records a single response for later comparison. The registration date is separately recorded as 2026-07-27. 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
The record lists NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar for verificator.cc. The source stores 192.162.199.184 as the observed address for verificator.cc. The registration date for verificator.cc is recorded as 2026-07-27. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-08-07. 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 verificator.cc record states that VirusTotal recorded 19 detections among 91 scanners on 2026-08-07. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-07. PhishDestroy remains a separate publisher catalogue entry in the stored record. NICENIC INTERNATIONAL GROUP CO., LIMITED is presented only as the recorded registrar, while 192.162.199.184 is presented only as the observed address. The supported conclusion is bounded to the exact stored observations for verificator.cc. Any statement beyond those source values would require additional dated material.
Recommended Actions
Use a known service address obtained separately from this report and avoid submitting sensitive information to verificator.cc during review. Defenders can retain the exact verificator.cc hostname as an indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL 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 verificator.cc; the stored record does not justify extending that rule to 192.162.199.184 or the NICENIC INTERNATIONAL GROUP CO., LIMITED registrar record.
Data Coverage
Данные сетевой безопасности
Процесс реагирования на угрозы
Проверка по блок-листам
10 внешних источников под наблюдением · снимок от 11.08.2026
8 внешних источников под наблюдением Совпадений нет
Сохранённые доказательства результата
Результат и атрибуция блокировки
- Результат
protected- Доступность
reachable_protected- Причина
cloudflare_challenge- Участник
- Cloudflare
- Механизм
challenge- Уверенность
- 85%
- Первое наблюдение
- Последнее наблюдение
SHA-256 доказательства c77941d131c1
Хронология обнаружения
-
Доступность
Первое сохранённое значение: Неизвестно
ca255b61650a -
Доступность
Неизвестно → Защищён
9518c3d9a530 -
Доступность
Защищён → Неизвестно
d8f7d37d7f95 -
Доступность
Неизвестно → Защищён
c77941d131c1
Сообщения сообщества
Сообщили 0 участников сообщества; впервые замечено 07.08.2026
- Уникальные URL
- 1
Технологии
Выявлено 4 технологии с высокой уверенностью
Анализ VirusTotal
Архивные доказательства
Анализ производительности сайта
Google PageSpeed Insights — mobile performance audit of verificator.cc · checked Aug 7, 2026
Похожие домены
Сохранено 79 похожих доменов
Показать все (67)
Повлиял ли на вас этот сайт?
Если вы ввели учетные данные, личную или платежную информацию или загрузили файл с этого домена, примите немедленные меры. Ниже приведены ресурсы, которые помогут вам сообщить об инциденте и защитить себя.
Сообщите об этом в местные органы власти
Выберите свою страну, чтобы получить официальные контакты по киберпреступности или создать проект жалобы →.
Проверить любой домен
Анализ угроз с использованием сохраненного черного списка, WHOIS, DNS и общедоступных доказательств сканирования.
Сканировать сейчасСообщить о фишинге
Добавляйте подозрительные домены в нашу базу данных угроз — защищайте сообщество
СообщитьПоток оперативных данных об угрозах
Недавние сообщения о фишинге и наблюдаемые изменения доступности
ОтслеживатьБудьте в курсе событий, берегите себя
Отслеживайте актуальные угрозы или оспорьте эту запись, если считаете, что это ложное срабатывание