Skip to security report
Domain security report
verificator.cc favicon

verificator.cc

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Unverified No conclusive current response is stored Observed · HTTP probe
VirusTotal detections: 19/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 1 Automated brand label: MetaMask
OTX: 5 refs Aug 7, 2026 MetaMask
API
Registrar
NiceNIC
Resolved IP
192.162.199.184
Registered
Jul 27, 2026
2 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 19. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
19 det.
OTX references
CF Radar
Malicious
URLScan
URLScan
Gridinsoft
1/100
ScamAdviser
Scamadviser
80/100Likely Safe
TLS Certificate
Within stored validity dates
Let's Encrypt · Hostname coverage not recorded
Age
3 mo New
PhishDestroy
DestroyList
Listed

Source evidence

10 · 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.

VirusTotal

19 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Gridinsoft

1/100

Observation time not recorded
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

1 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

5 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Observation time not recorded
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Scamadviser

80/100

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence Registrar context
CF Cloudflare Radar Verdict Malicious
Malware
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Evidence Summary

Critical
VirusTotal
19/91
OTX
5 community refs
URLScan
Stored capture

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.

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 & collection

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.

Recorded dataPartial recordUTC
VirusTotal
19 / 91 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
5 · community references
External blocklists
1 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Gridinsoft
1/100 · provider trust scoreCollection time not recorded
Scamadviser
80/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
192.162.199.184 · 0 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
100/100 · mobile performance
Availability history
71 · stored state changes
Source observation history
2 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

1 · external source matches

Public Blocklist Status

Domain, network & archive

NICENIC INTERNATIONAL GROUP CO., LIMITED · 192.162.199.184 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 1/100 1 report Port Scan checked Oct 6, 2026
OTX tags 2026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
RegistrationCreated Jul 27, 2026 (82d · New)
Elapsed Since First Report 31 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Unverified.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 7, 2026
DOM Analysisanalyzed Aug 7, 2026score 100/1001 brand signal
Submitted URLhttp://verificator.cc/

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
192.162.199.184
Network ASN
AS214351
Organization
Femo IT Solutions Limited
Observed location
Frankfurt Am Main, DE
Server header
Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-07-31 10:03:36
Valid until
2026-10-29 10:03:35
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-08-07 10:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc1bd3953e1e48bb819aadef79e4be1d7cee000e8dce362c551cfcd71399b0949

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-17 04:27:13 UTC

Primary outcome Registration hold observed reason: Registrar clientHold 95% confidence
Attribution NICENIC INTERNATIONAL GROUP CO., LIMITED mechanism: Registrar clientHold source: Rdap Status Collector
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Registrar clientHold
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-17 10:57:09 UTC
RDAP registration Registrar clientHold NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765 RDAP HTTP 200 source: Rdap Status Collector clientDeleteProhibitedclientHoldclientTransferProhibited expires 2027-07-27 03:42:47 UTC checked 2026-10-17 04:27:13 UTC
Registrar action marker verified clientHold marker NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765 causal link to our report not established
Observed timeline last reachable: 2026-08-10 22:59:25 UTC current episode first observed: 2026-08-11 12:53:26 UTC observed RIP window: 2026-08-10 22:59:25 UTC → 2026-08-11 12:53:26 UTC · 13.90h midpoint estimate ≈ 2026-08-11 05:56:25 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

19 / 91 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Cluster25
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
SafeToOpen
Seclookup
SOCRadar
Sophos
URLQuery
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of verificator.cc · checked Aug 7, 2026

100
Good
Performance
FCP
0.97s
First Contentful Paint
LCP
0.97s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.35s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details18

Registration evidence

RDAP statuses
clientdeleteprohibited · clienthold · clienttransferprohibited
RDAP response
200
Registrar in registration evidence
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registrar IANA ID
3765
Expiration recorded by RDAP
Registration observation
Registration source
rdap_status_collector

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
13.9
Estimate basis
Bounded by observations
Estimate precision
Medium

Registrar action record

Recorded actor
NICENIC INTERNATIONAL GROUP CO., LIMITED
Actor IANA ID
3765
Action observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

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(

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

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.
  1. Domain Status Transition 2026-09-07 02:30:57 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-08-07 08:49:57 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 192.162.199.184.
Stored observation history73

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

Earlier observations 68
  1. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  6. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  10. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  13. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  14. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  15. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  16. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  17. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  18. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  19. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  20. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  21. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  22. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  23. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  24. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  25. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  26. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  27. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  28. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  29. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  30. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  31. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  32. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  33. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  34. Availability monitor · Recorded state

    held→Unknown

    origin_unreachable · http_5xx

  35. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  36. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  37. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  38. Availability monitor · Recorded state

    dns_inactive→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  39. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  40. Availability monitor · Recorded state

    dns_inactive→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  41. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  42. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  43. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  44. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  45. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  46. Availability monitor · Recorded state

    held→Unknown

    origin_unreachable · http_5xx

  47. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  48. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  49. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  50. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  51. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  52. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  53. Availability monitor · Recorded state

    held→Unknown

    probe_inconclusive

  54. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  55. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  56. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  57. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  58. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  59. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  60. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  61. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  62. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  63. Availability monitor · Recorded state

    Unknown→held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  64. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  65. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  66. Availability monitor · Recorded state

    held

    registrar_client_hold · NICENIC INTERNATIONAL GROUP CO., LIMITED · client_hold

  67. Availability monitor · Recorded state

    Reachable→Unavailable

  68. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Monitoring

15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
verificator.cc detected and queued for full analysis
Aug 7, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 6, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Aug 7, 2026
VirusTotal
19/91 recorded on VirusTotal
Aug 7, 2026
Blocklist Detection
Found in 1 blocklist: MetaMask
Oct 17, 2026
OTX Community References
5 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 5, 2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
CF Radar: Malicious
Cloudflare Radar classified this domain as malware
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 7, 2026
DestroyList Published
Aug 7, 2026
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 0 stored notification records Unverified

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including verificator.cc)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: verificator.cc

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.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/verificator.cc"
  title="PhishDestroy threat report for verificator.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>