Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T08:04:35Z. Retrieved (as stored): 2026-11-05T01:06:31Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
pomoc-medfile.app favicon

pomoc-medfile.app

In short

PhishDestroy first recorded pomoc-medfile.app on 2026-11-04. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T08:04:35Z. Retrieved (as stored): 2026-11-05T01:06:31Z.

Review the evidence
Registrar
IndiaPDR
Resolved IP
Russia192.144.57.74Hosting technology LTD
Registered
May 27, 2026
First observed
Nov 4, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Spamhaus DBL: phishing domain
VirusTotal
17 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 85
Page captures
2
open gallery
Domain age
161 days
registered 2026-05-27 according to WHOIS
OTX: 3 refs Nov 4, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded pomoc-medfile.app on 2026-11-04. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T08:04:35Z. Retrieved (as stored): 2026-11-05T01:06:31Z. Risk: critical (100/100). Registrar: PDR. Status: Last known active. Hosting: Hosting technology LTD. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
Russia192.144.57.74Hosting technology LTD
Registrar
IndiaPDR
Registered
May 27, 2026
OTX
3 community refs
Page captures
2
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for pomoc-medfile.app. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 17 / 92 · OTX 3 references 6 sources

VirusTotal

17 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
14
Suspicious
3
Undetected
32

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
spam
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    192.144.57.74
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.desec.io
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.desec.org
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    get.desec.io
    Value
    get.desec.io

DNS records observed

JARM fingerprint

21d19d00021d21d00042d43d00000091f9827a8676a9d9f27d421962a09b5d

Certificate

Subject alternative names
  • doctor-helper-global.ru
Issuer
Let's Encrypt / YR2
Serial
5e3b5653ea215495bfb4c05a8765abbc6d1
SHA-256
18623ee3f310c5d91f2f5b3c70b621485e042ea578a2e63360c1adc659f70315
Subject
doctor-helper-global.ru
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
First seen
2026-05-27T07:51:58Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "192.144.57.74"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.desec.io"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.desec.org"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "get.desec.io",
        "value": "get.desec.io"
    }
]
Dns at
2026-11-01T10:22:13Z
Jarm
21d19d00021d21d00042d43d00000091f9827a8676a9d9f27d421962a09b5d
Certificate
{
    "san": [
        "doctor-helper-global.ru"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5e3b5653ea215495bfb4c05a8765abbc6d1",
    "sha256": "18623ee3f310c5d91f2f5b3c70b621485e042ea578a2e63360c1adc659f70315",
    "subject": "doctor-helper-global.ru",
    "valid_to": "2027-01-23T11:51:56Z",
    "valid_from": "2026-10-25T11:51:57Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-07-27T00:05:21Z",
        "registration": "2026-05-27T06:45:18Z",
        "registrar expiration": "2027-05-27T06:45:18Z",
        "last update of RDAP database": "2026-10-27T13:28:59Z"
    },
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "registrar_iana_id": "303"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
17
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Chong Lua Dao","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Lionic","Seclookup","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-11-01 08:04:35
checked_at
2026-11-05 02:06:37
fetched_at
2026-11-05 01:06:37
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

8fa87873-cd57-4835-9766-eab523ac2094

Final URL

https://pomoc-medfile.app/

Navigation history

  • URL
    https://pomoc-medfile.app/
    Status
    0

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    pomoc-medfile.app
    Type
    A
    Value
    192.144.57.74

DNSSEC valid

No

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
Updated
Expires
Nameservers
  • ns1.desec.io
  • ns2.desec.org
Original source fields · JSON
Uuid
8fa87873-cd57-4835-9766-eab523ac2094
Final url
https://pomoc-medfile.app/
History
[
    {
        "url": "https://pomoc-medfile.app/",
        "status": 0
    }
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "pomoc-medfile.app",
        "type": "A",
        "value": "192.144.57.74"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2026-05-27T06:45:18Z",
    "updated": "2026-06-01T06:45:18Z",
    "expires": "2027-05-27T06:45:18Z",
    "nameservers": [
        "ns1.desec.io",
        "ns2.desec.org"
    ]
}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 85

Open report
URLScanOriginal source recordObserved: 6 fields

Observed: · Retrieved:

Report ID

019ed3cb-0bf7-7499-9865-e53df86fabd9

Final URL

https://pomoc-medfile.app/

Domain age, days

20

Registered domain age, days

20

Page requests

1

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
85
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
019ed3cb-0bf7-7499-9865-e53df86fabd9
Final url
https://pomoc-medfile.app/
Domain age days
20
Apex age days
20
Requests
1
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 11 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Trackers

Requests
34

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    157.53.224.1
    Host
    ns2.desec.org
  • IP address
    45.54.76.1
    Host
    ns1.desec.io
DNS zone
pomoc-medfile.app

Location

IP address
192.144.57.74
ASN
48282
Organization
Hosting technology LTD
City
Moscow
Country
RU

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
doctor-helper-global.ru

DNS records

A
  • 192.144.57.74
NS
  • ns1.desec.io
  • ns2.desec.org
SOA
Primary nameserver
get.desec.io
Hostmaster
get.desec.io
Serial
2026055668
Refresh, seconds
86400
Retry, seconds
3600
Expiry, seconds
2419200
Minimum TTL, seconds
3600

DNSSEC

DS record
No
RRSIG
No
DNSKEY
Yes

IP lookup

IP address
192.144.57.74
IP version
4
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Trackers
{
    "requests": 34
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "157.53.224.1",
            "host": "ns2.desec.org"
        },
        {
            "ip": "45.54.76.1",
            "host": "ns1.desec.io"
        }
    ],
    "zone": "pomoc-medfile.app"
}
Location
{
    "ip": "192.144.57.74",
    "asn": "48282",
    "org": "Hosting technology LTD",
    "city": "Moscow",
    "country": "RU"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "doctor-helper-global.ru"
}
DNS records
{
    "A": [
        "192.144.57.74"
    ],
    "NS": [
        "ns1.desec.io",
        "ns2.desec.org"
    ],
    "SOA": "{\"nsname\": \"get.desec.io\", \"hostmaster\": \"get.desec.io\", \"serial\": 2026055668, \"refresh\": 86400, \"retry\": 3600, \"expire\": 2419200, \"minttl\": 3600}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": true
}
Get ip
{
    "ip": "192.144.57.74",
    "family": 4
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Malware Security threats
View full Cloudflare Radar report

Questions about pomoc-medfile.app

Is pomoc-medfile.app legit?

PhishDestroy rates pomoc-medfile.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T08:04:35Z. Retrieved (as stored): 2026-11-05T01:06:31Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is pomoc-medfile.app safe to connect a wallet?

This report does not record which wallet requests pomoc-medfile.app makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used pomoc-medfile.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

URLScan · 2026-11-04 1 / 2
SourceURLScan · 2026-11-04
Recorded
StateStored capture
HTTP status200
Final URLhttps://pomoc-medfile.app/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 79 days

Domain details

Domain
IP Reputation Russia192.144.57.74 abuse score 0/100 0 reports checked Nov 4, 2026
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar PDR IN(IN)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for pomoc-medfile.app →
RegistrationCreated May 27, 2026 (161d) — Expires May 27, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
Submitted URLhttp://pomoc-medfile.app/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Russia192.144.57.74
Network ASN
AS48282
Organization
Hosting technology LTD
Observed location
RussiaMoscow, RU

Nameservers 1

  • ns2.desec.org

SOA

  • nsname: get.desec.io
  • hostmaster: get.desec.io
  • serial: 2026055668
  • refresh: 86400
  • retry: 3600
  • expire: 2419200
  • minttl: 3600

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-25 11:51:57
Valid until
2027-01-23 11:51:56
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint18623ee3f310c5d91f2f5b3c70b621485e042ea578a2e63360c1adc659f70315
Certificate names · 1 SAN
  • doctor-helper-global.ru

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

viewdns.info · 192.144.57.74rapiddns.io
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.pomoc-medfile.appDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 17 detections
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
Seclookup
Gridinsoft
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of pomoc-medfile.app · checked Nov 4, 2026

81
Needs Work
Performance
FCP
1.07 s
First Contentful Paint
LCP
3.84 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1 ms
Total Blocking Time
SI
7.23 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://pomoc-medfile.app/
Doctor Helper
Справочник антибиотиков и ИИ-расшифровщик антибиотиограммы — всё в одном сервисе для врачей
Response
HTTP 200
HTML body
172.6 KB
Compressed
49.4 KB
Links
18 internal · 3 external
Detected technologies
reactnginx
Selected response headers
Server: nginx/1.27.5
Content-Type: text/html; charset=utf-8
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding: gzip
X-Powered-By: Next.js
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: d48f3663727e79245fc7a5a5084293314a934c6661705770a5e8c23de15d3143
Saved response-header values · 10
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Wed, 04 Nov 2026 20:49:32 GMT
Link
; rel=preload; as="font"; crossorigin=""; type="font/woff2", ; rel=preload; as="font"; crossorigin=""; type="font/woff2"
Server
nginx/1.27.5
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
X-Powered-By
Next.js

Values retained by the collector; long values may be shortened during collection.

Archived

Captured network requests

Network requests: 1 SHA-256 hashes: 0 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-04 19:40 UTC.

Open this scan on URLScan 019ed3cb-0bf7-7499-9865-e53df86fabd9 ↗

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-02 04:28:07
All retained availability observations1

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 20:41:33.599088
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    pomoc-medfile.app detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 85
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Malware, Security threats
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    pomoc-medfile.app

    View source
  4. VirusTotal

    17/92 engine detections

    View source
  5. URLScan

    Malicious · engine verdict · score 85

    View source
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

pomoc-medfile.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious OTX 3 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 pomoc-medfile.app)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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 →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA 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/pomoc-medfile.app"
  title="PhishDestroy threat report for pomoc-medfile.app"
  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>