VirusTotal
16 / 92 engine detections
Open report“Здоровье и медицина: Бразилия · 4hg83f0.shop”
16 / 92 engine detections
Open reportMalicious
Open reportDBL_PHISH
Scan report
Open report5 community references
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has added 4hg83f0.shop to its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19. No page title or specific content was recorded at the time of observation.
The current evidence does not identify a particular malicious mechanism. Suspicious domains like this are often used for phishing, credential harvesting, or fraudulent offers, but the listing and detections alone do not prove any specific activity.
VirusTotal reported 16 detections out of 92 scanning engines on 2026-10-19, with vendors including AlphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker and Fortinet. Google Safe Browsing checked the domain on 2026-10-19 and did not flag it. External public blocklists showed no entries for the domain on the same date. PhishDestroy’s internal blocklist marked the domain as suspicious on 2026-10-19. OTX listed five pulses referencing the domain on 2026-10-19.
The domain was registered on 2026-07-07 through Global Domain Group LLC. The recorded IP address associated with the domain is 195.234.5.142. No further network or hosting details are available.
Avoid visiting or interacting with 4hg83f0.shop and do not submit any credentials or personal information. Users who may have entered data should change affected passwords and monitor accounts for unusual activity. Security teams should add a rule to block traffic to this exact domain and review logs for any connections from internal hosts.
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.
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.
fred.ns.cloudflare.comindie.ns.cloudflare.commail.4hg83f0.shoppriority 1Location describes the IP network.
fbc518987364f417d9d7fd2b029937a6700816dbdfb6c6e407fa3618974d9045Saved 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 4hg83f0.shop · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://4hg83f0.shop/https://4hg83f0.shop/Server: nginx/1.18.0 (Ubuntu)Content-Type: text/html; charset=utf-8Cache-Control: public, max-age=600, must-revalidateContent-Encoding: gzipsummary_large_imagepublic, max-age=600, must-revalidatekeep-alivegziptext/html; charset=utf-8Mon, 19 Oct 2026 20:07:32 GMTW/"6accfd69-2b9e"Mon, 12 Oct 2026 15:31:53 GMTnginx/1.18.0 (Ubuntu)chunkedValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
5 community references
View sourceNo threat flag
View source16/92 engine detections
View sourcePD-20261019-218458
4hg83f0.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
4hg83f0.shop
PD-20261019-218458 Recipient: abuse@globaldomaingroup.com 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 ↗
4hg83f0.shop)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
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.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
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.