VirusTotal
23 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Ikov | Fresh World”
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.
23 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
DBL_MALWARE
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
20 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA 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.
Report stored; verdict not recorded
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.
0 external matches
DetailsA 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.
ikovrsps.com was observed in a PhishDestroy internal listing on 2026-10-16, documenting its inclusion in a publisher-owned catalogue. On the same date, the domain was also referenced in OTX with a total of 20 pulses, providing further context for its security profile.
On 2026-10-16, PhishDestroy recorded ikovrsps.com in its internal listing. OTX referenced the domain with 20 pulses on 2026-10-16. VirusTotal checked the domain on 2026-10-15, recording 23 detections out of 92 total scanners. The domain was registered with Ultahost, Inc. on 2026-01-22.
PhishDestroy contains a record of ikovrsps.com as an internal listing, which documents its presence in a publisher-maintained catalogue. VirusTotal provides a measurement of how many security scanners detected the domain, reflecting the results of automated analysis. OTX records the domain's presence in 20 pulses, which are groupings of related security observations. These sources together offer a technical snapshot from multiple perspectives, covering both internal and external intelligence.
For ongoing monitoring of ikovrsps.com, retain the PhishDestroy internal listing and VirusTotal detection records for future comparison. Use the OTX pulse count as an additional reference point to track changes in external security intelligence. Reassess these records periodically to maintain an up-to-date understanding of the domain's security context.
19 · datasets with records / 12 · 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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/ikovrspsStored page referenceIoC extraction recorded 2026-10-16 04:00:06 UTC
0 · external source matches
Ultahost, Inc. · 195.26.86.171 · DNS, TLS and retained responses
tani.ns.cloudflare.comtosana.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.ikovrsps.comDomain recordThe original observation time is not recorded for these hostnames.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
The scanner received HTTP 404 or 410 for this file.
/sitemap.xml
The scanner received HTTP 404 or 410 for this file.
/.well-known/security.txt
The scanner received HTTP 404 or 410 for this file.
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.
No live-check result has been retained.
1 · outbound report records
195.26.86.171.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown
probe_inconclusive
Reachable
10 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.
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
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 ↗
ikovrsps.com)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.
Captured title: “Ikov | Fresh World”. Apparent target: Discord.
VirusTotal detections for ikovrsps.com: 23 (2026-10-16 02:40:06 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.