VirusTotal
19 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
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.
19 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
1/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
1 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
5 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
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.
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.
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.
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.
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.
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.
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.
22 · datasets with records / 9 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
1 · external source matches
NICENIC INTERNATIONAL GROUP CO., LIMITED · 192.162.199.184 · DNS, TLS and retained responses
Location describes the IP network.
c1bd3953e1e48bb819aadef79e4be1d7cee000e8dce362c551cfcd71399b0949Saved 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 verificator.cc · checked Aug 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='verificator.cc', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
No live-check result has been retained.
Collection history, report status and investigation channels
192.162.199.184.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
held→Unknown
origin_unreachable · http_5xx
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
origin_unreachable · http_5xx
held→dns_inactive
dns_nxdomain
dns_inactive→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
held→dns_inactive
dns_nxdomain
dns_inactive→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
held→Unknown
origin_unreachable · http_5xx
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
origin_unreachable · http_5xx
held→dns_inactive
dns_nxdomain
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
held→Unknown
probe_inconclusive
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
held→dns_inactive
dns_nxdomain
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
held→dns_inactive
dns_nxdomain
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
held→dns_inactive
dns_nxdomain
Unknown→held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
dns_inactive→Unknown
probe_inconclusive
held→dns_inactive
dns_nxdomain
held
registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold
Reachable→Unavailable
Unknown
15 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.
Shared hosting, registrar records and related domains
79 stored lookalike domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
verificator.cc)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
Stored evidence snapshot. Source timestamps appear where available.
VirusTotal detections for verificator.cc: 19 (2026-08-07 08:50:00 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.