PhishDestroy first recorded diabetespakistan.com on 2026-10-25. Stored VirusTotal result: 13/92 engines flagged. Malicious: 9. Suspicious: 4. Analysis time (as stored): 2026-10-24 14:45 UTC. Retrieved (as stored): 2026-10-25 09:13 UTC.
Page title: “DIP – Care Until Cure!”
More about the sources
Recorded security signals
Stored VirusTotal result: 13/92 engines flagged. Malicious: 9. Suspicious: 4. Analysis time (as stored): 2026-10-24 14:45 UTC. Retrieved (as stored): 2026-10-25 09:13 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@hostinger.com. The latest stored availability evidence still shows the domain reachable; 28 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
28 days
Reports sent
1
Latest case ID
PD-20261025-1139C4
Current status
HTTP 200 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded diabetespakistan.com on 2026-10-25. Stored VirusTotal result: 13/92 engines flagged. Malicious: 9. Suspicious: 4. Analysis time (as stored): 2026-10-24 14:45 UTC. Retrieved (as stored): 2026-10-25 09:13 UTC. Risk: critical (evidence score 100/100). Registrar: Dynadot. Status: Last known active. Hosting: Hostinger International Limited. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
The captured screenshot shows a health page headed Diabetic's Institute Pakistan, topped by a banner reading For Appointment Call Us with a phone number, body copy claiming professional doctors, psychologists and rehab care, and an embedded video player. PhishDestroy listed the domain after VirusTotal flagged it as malicious. The domain was first seen on 2026-10-25.
How the scam works
No form fields appeared in the capture; the page instead pushed visitors toward the appointment phone number shown in the banner, a pattern used to collect personal and health details during an unsolicited call. Paired with promises of treatment and rehab care, it enables social engineering of people seeking diabetes or addiction support.
Evidence
The screenshot shows the appointment call banner, the institute branding with city names, and the treatment claims described above. urlscan returned a non-malicious overall verdict with an engine ML score of minus 19 on 2026-10-25 and followed a 307 redirect from HTTP to HTTPS. VirusTotal flagged the domain as malicious, with phishing labels from Kaspersky and Sophos, and Cloudflare Radar tagged it malware on 2026-10-25, while Spamhaus listed nothing on 2026-10-25, Google Safe Browsing was not flagged on 2026-10-26, external blocklists showed zero entries with PhishDestroy's internal list matching on 2026-10-26, and OTX recorded 5 pulses on 2026-10-25. Inspection found a WordPress page running jQuery and Elementor with Contact Form 7 alongside Google, Google Marketing Platform and YouTube trackers, and 10 distinct script SHA256 hashes are recorded, for example cb6f2d32c49d, for campaign pivoting.
Infrastructure
Notable weaknesses first: HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP, COEP and CORP are all absent, Content-Security-Policy carries only upgrade-insecure-requests, SPF is present with no DKIM or DMARC, and DNSSEC is unsigned. The domain was registered through Dynadot Inc on 2007-12-14 and recorded on Hostinger International Limited infrastructure, with no WAF shown in the capture. TLS 1.3, TLS_AES_256_GCM_SHA384, forward secrecy, ALPN h2; a CAA record is present.
What to do
If you called the number in the banner or shared personal or health information, stop further contact, monitor for follow-up approaches, and report the captured site to your provider. Do not send payments or documents requested during such calls. Defenders should block diabetespakistan.com at the proxy, mail and endpoint layers and keep it on deny lists.
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.
PhishDestroy assesses diabetespakistan.com as a fake clinic appointment lure soliciting appointment calls from visitors.
AI summary
Overview The captured screenshot shows a health page headed Diabetic's Institute Pakistan, topped by a banner reading For Appointment Call Us with a phone number, body copy claiming professional doctors, psychologists and rehab care, and an embedded video player. PhishDestroy listed the domain after VirusTotal flagged it as malicious. The domain was first seen on 2026-10-25. How the scam works No form fields appeared in the capture; the page instead pushed visitors toward the appointment phone number shown in the banner, a pattern used to collect personal and health details during an unsolicited call. Paired with promises of treatment and rehab care, it enables social engineering of people seeking diabetes or addiction support. Evidence The screenshot shows the appointment call banner, the institute branding with city names, and the treatment claims described above. urlscan returned a non-malicious overall verdict with an engine ML score of minus 19 on 2026-10-25 and followed a 307 redirect from HTTP to HTTPS. VirusTotal flagged the domain as malicious, with phishing labels from Kaspersky and Sophos, and Cloudflare Radar tagged it malware on 2026-10-25, while Spamhaus listed nothing on 2026-10-25, Google Safe Browsing was not flagged on 2026-10-26, external blocklists showed zero entries with PhishDestroy's internal list matching on 2026-10-26, and OTX recorded 5 pulses on 2026-10-25. Inspection found a WordPress page running jQuery and Elementor with Contact Form 7 alongside Google, Google Marketing Platform and YouTube trackers, and 10 distinct script SHA256 hashes are recorded, for example cb6f2d32c49d, for campaign pivoting. Infrastructure Notable weaknesses first: HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP, COEP and CORP are all absent, Content-Security-Policy carries only upgrade-insecure-requests, SPF is present with no DKIM or DMARC, and DNSSEC is unsigned. The domain was registered through Dynadot Inc on 2007-12-14 and recorded on Hostinger International Limited infrastructure, with no WAF shown in the capture. TLS 1.3, TLS_AES_256_GCM_SHA384, forward secrecy, ALPN h2; a CAA record is present. What to do If you called the number in the banner or shared personal or health information, stop further contact, monitor for follow-up approaches, and report the captured site to your provider. Do not send payments or documents requested during such calls. Defenders should block diabetespakistan.com at the proxy, mail and endpoint layers and keep it on deny lists. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a1723a-fada-735a-ba9b-1b6d0dcaac82/ Cloudflare Radar report: https://radar.cloudflare.com/scan/77fe39cd-a229-4050-9ee4-f66cdf379926 URLQuery report: https://urlquery.net/report/ade85eea-d450-49af-8524-a142fb300229 Stored capture screenshot: https://urlscan.io/screenshots/01a1723a-fada-735a-ba9b-1b6d0dcaac82.png Cloudflare Radar screenshot (2026-10-25T08:36:22Z): https://screenshots.phishdestroy.io/cf/77fe39cd-a229-4050-9ee4-f66cdf379926.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/ade85eea-d450-49af-8524-a142fb300229.png URLScan screenshot (2026-09-05T08:45:28Z): https://screenshots.phishdestroy.io/us/01a070be-5c9b-720e-b0f8-f3c48f3e1010.png URLScan capture report: https://urlscan.io/result/01a070be-5c9b-720e-b0f8-f3c48f3e1010/ URLScan screenshot (2026-09-05T09:09:28Z): https://screenshots.phishdestroy.io/us/01a070d4-5a44-75c2-aaa7-65e451b40f57.png URLScan capture report: https://urlscan.io/result/01a070d4-5a44-75c2-aaa7-65e451b40f57/ URLScan screenshot (2026-09-06T09:30:50Z): https://screenshots.phishdestroy.io/us/01a0760e-35b6-71bd-9b18-cf5f9a5ecf73.png URLScan capture report: https://urlscan.io/result/01a0760e-35b6-71bd-9b18-cf5f9a5ecf73/ URLScan screenshot (2026-10-25T08:28:57Z): https://screenshots.phishdestroy.io/us/01a1722d-398d-711f-b558-b2f3d0d0f0e2.png URLScan capture report: https://urlscan.io/result/01a1722d-398d-711f-b558-b2f3d0d0f0e2/ VirusTotal report: https://www.virustotal.com/gui/domain/diabetespakistan.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=diabetespakistan.com Archived copy: https://web.archive.org/web/20261025082207/https://diabetespakistan.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
According to Tranco this site has a low rank This website has been marked as threat by DNSFilter in the last 30 days
The SSL certificate is valid This website is (very) old The website seems to offer health information.
Network Security Intelligence
Cloudflare Radar VerdictMalicious
Malware Malware Security threats
Questions about diabetespakistan.com
Is diabetespakistan.com legit?
PhishDestroy rates diabetespakistan.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-25. Stored VirusTotal result: 13/92 engines flagged. Malicious: 9. Suspicious: 4. Analysis time (as stored): 2026-10-24 14:45 UTC. Retrieved (as stored): 2026-10-25 09:13 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is diabetespakistan.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on diabetespakistan.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used diabetespakistan.com?
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
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
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.
IP Reputation147.93.22.560/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing.0 reportschecked 2026-10-25
Certificate fingerprint935cb988af6070fc35a82f9a68a644b7c220454e54599427472f9f0d261cbb42Certificate names · 2 SANs
diabetespakistan.com
www.diabetespakistan.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:33 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:33 UTClast content: 2026-11-22 11:33 UTC
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.
Recorded subdomains2
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
new.diabetespakistan.comDomain record
www.diabetespakistan.comDomain record
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
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-10-29 01:57 UTC.
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
7 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+6888 d 19 h
Added to PhishDestroy+17 h 36 min
First abuse report sent+36 min
Reported 6889 d 13 h after registration
AlienVault OTX
5 community references
+13 min
Hostinger
Took action
+4 min
Abuse report sent
PD-20261025-1139C4 · Receipt 82918
abuse@hostinger.com
+12 min
URLScan
Page captured
+23 min
Wayback Machine
Page archived
same minute
Added to PhishDestroy
diabetespakistan.com
+17 h 36 min
VirusTotal
13/92 engine detections
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
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. Secure your accounts and funds first, then report. 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.
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
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 diabetespakistan.com)
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)
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
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.
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.