⚠️
This domain has been flagged as malicious
Listed in 1 public blocklist and flagged by PhishDestroy threat intelligence — no VirusTotal vendors have flagged it yet. Exercise extreme caution — do not enter personal information or connect wallets. Generate an official AI-powered complaint letter to file with cybercrime authorities.
azkaariba.github.io favicon

azkaariba[.]github[.]io

Domain Security & Threat Intelligence Report
Content unavailable Jul 29, 2026 Unavailable since Jul 29, 2026 1 Blocklist 1h to unavailable US US + more
58 Risk Score
PhishDestroy AI
HIGH
Ref
FEC4A46C
Score
58/100
Engine
PD-4 Turbo
Analysis of azkaariba[.]github[.]io indicates that the domain resolves to the IP address 185.199.108.153 and was registered through GitHub, Inc. The domain is currently listed on one security blocklist and has been explicitly blocked by the PhishDestroy service. VirusTotal records show that the domain was examined by 91 scanning vendors, none of which reported a detection at the time of analysis. No nameserver information is available (NS_NOT_FOUND), and there is no publicly disclosed page title, SSL certificate details, or HTTP response data.

The available intelligence confirms that the domain remains active as of the report date, July 29, 2026, and continues to be flagged for generic phishing activity. Uncertainty remains regarding the specific content hosted on the site, the presence of any TLS encryption, and whether additional detection services have observed malicious payloads.

Defenders should treat the domain as hostile: network controls ought to block DNS resolution and HTTP/S traffic to the domain and its associated IP, security monitoring should alert on any outbound connections to 185.199.108.153, and incident response teams should consider adding the domain to internal blocklists. Continuous re‑evaluation is advised, as the lack of detections from the 91 vendors does not guarantee the absence of malicious behavior, and future changes to the hosted content could alter the risk profile.
VirusTotal
VirusTotal
0 det.
URLScan
URLScan
SSL
Let's Encrypt
Observed status
Content unavailable 404
PhishDestroy
DestroyList
Listed
Data coverage VirusTotal no detections URLQuery no detections OTX no pulses CF Radar no data URLScan report ready DNS blocks none SSL valid, 35d WHOIS not parsed Screenshot not captured Redirect chain not probed

Threat Response Pipeline

Discovery
Checks
Reports
Availability
12/13
Pre-emptive Discovery & Ingestion
Threat Ingested
1/1 ✓
Threat Ingested
azkaariba.github.io detected and queued for full analysis
Jul 29, 2026
Threat Intelligence Checks
URLScan.io Snapshot · Cloudflare Radar · VirusTotal · Google Safe Browsing · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable
8/8 ✓
URLScan.io Snapshot
Submitted to urlscan.io — screenshot, DOM & HTTP transactions captured
Jul 29, 2026
Cloudflare Radar
Scanned via Cloudflare Radar — DNS, certificates & network data
VirusTotal
91 vendors checked on VirusTotal — no vendor detections recorded at check time
Jul 29, 2026
Google Safe Browsing
Jul 29, 2026
Blocklist Detection
Found in 1 blocklist: OpenPhish
Jul 29, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Jul 29, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results
Jul 29, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established
Jul 29, 2026
Notification Records
Abuse Report Pending
PENDING
Abuse Report Pending
Will be sent to registrar (GitHub, Inc.) & hosting
Publication & Availability
DestroyList Published · Content Observed Unavailable · Time to First Unavailability
3/3 ✓
DestroyList Published
Jul 29, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change
Jul 29, 2026
Time to First Unavailability
1 hour elapsed from detection to the first unavailable observation

Public Blocklist Status

2
Confirmed in 2 datasets: PhishDestroy + 1 independent public blocklist — OpenPhish
10 external threat databases checked; 1 matched. Last synchronized Jul 29, 2026. PhishDestroy database match: confirmed.

Evidence Capture

Live Snapshot
2026-07-29 02:38 UTC
Malicious
Forensic screenshot of azkaariba.github.io showing the phishing page layout
IP: 185.199.108.153
GitHub, Inc.
Let's Encrypt

Domain Intelligence

Domainazkaariba.github.io
Registrar GitHub
IP Address 185.199.108.153 US
GeoUS San Francisco, US
Network AS54113 Fastly, Inc.
HTTP Status404 Not Found
Time to First Unavailability 1h
What we count Elapsed time from the first stored abuse report to the first observation that azkaariba.github.io was unavailable. This does not establish the cause.
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 detailsDNS, SSL SANs, timestamps
First DetectedJul 29, 2026
NameserversNS_NOT_FOUND
TLS Fingerprint32491b26bfaf7bfb556029ef32299ac4374db34d…
Shared-IP Neighbors · 8 other domains
185.199.108.153 is hosting 8 other flagged phishing/scam domains in our database. Co-hosting on a non-CDN IP is a strong bulletproof-hosting signal.
kenagent.xyz Active gaia.infiniti-ia.com Active eltor.app Active xoxminer.com Active usdtcportal.xyz Active trustwallet-access.com Active suika3.vn Active recovery.sequence.app Active
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of azkaariba.github.io · checked Jul 29, 2026

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

Evidence & External Reports

Were You Affected by This Site?

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 you have interacted with this domain, entered personal information, or connected a cryptocurrency wallet — take immediate action. Below are resources to help you report the incident and protect yourself.

Beware of recovery scammers! After being scammed, criminals may contact you again pretending to be "recovery agents," lawyers, or investigators who claim they can retrieve your lost funds — for a fee. This is a second scam. No legitimate service will ask for upfront payment to recover stolen crypto. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or generate an AI-powered complaint →

Select your country...
180+ countries
Zero-PII — your data never leaves the browser AI writes in your language

Related Domain Reports

lohithp2804-star.github.io
lohithp2804-star.github.io
6 detections
myspotifypremium.info
myspotifypremium.info
15 detections
absicherung-de.com
absicherung-de.com
14 detections
login-my-facebook.blogspot.com
login-my-facebook.blogspot.com
11 detections
sso-ca-netcoins---autth.webflow.io
sso-ca-netcoins---autth.webflow.io
13 detections
rss.sayler.at
rss.sayler.at
17 detections

Other Domains on 185.199.108.153 6 phishing domains

This IP hosts multiple phishing domains — infrastructure shared across campaigns

atendimento-itau-0800.com.br favicon atendimento-itau-0800.com.br 22/95 danielackermann69.github.io favicon danielackermann69.github.io 21/95 muniraattar3.github.io favicon muniraattar3.github.io 21/95 shubham25b01010593.github.io favicon shubham25b01010593.github.io 20/95 azerty-46.github.io favicon azerty-46.github.io 20/95 f-case-feedback-appeal.github.io favicon f-case-feedback-appeal.github.io 20/95

More Domains at GitHub 6 flagged

lohithp2804-star.github.io favicon lohithp2804-star.github.io 6/95 rashi-garg904.github.io favicon rashi-garg904.github.io judiblessing21-ship-it.github.io favicon judiblessing21-ship-it.github.io vivek-chaudhary-24.github.io favicon vivek-chaudhary-24.github.io 5/95 okegaskepin-lab.github.io favicon okegaskepin-lab.github.io sakshamsinghal2507.github.io favicon sakshamsinghal2507.github.io

About This Report: azkaariba.github.io

This report presents the latest stored evidence available to PhishDestroy. Source timestamps are shown where available; availability and vendor verdicts can change after collection.

azkaariba.github.io has been listed on PhishDestroy as a suspicious domain. Scanned by 91 security vendors — automated detections may take time to update. PhishDestroy threat analysts continue to monitor this domain.

If you believe this listing is inaccurate, you can submit an appeal. For more information about our methodology, visit our FAQ page.

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

Live Threat Feed Appeal This Listing

Recommendations & Advice for Victims

An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with azkaariba.github.io — act now.

What should I do immediately?
Urgent
  • Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
  • Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
  • 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

According to the FBI, the most important details are transaction data:

  • Cryptocurrency addresses — scammer's wallet (e.g., 0x5856...35985)
  • Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
  • Transaction ID (hash) — the unique blockchain transaction identifier
  • 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 azkaariba.github.io)
  • 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)
  • Chainabuse — flag scam wallets across exchanges & platforms
  • Your crypto exchange — contact Coinbase/Binance/Kraken support to freeze scammer's address
  • Local police — creates an official record, even if they can't act immediately

The FBI recovered over $1 billion in crypto fraud in 2024 thanks to victim reports. Your report matters.

How do crypto scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — victims targeted AGAIN by fake "recovery agents" demanding upfront fees. Always a scam
  • Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
  • Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Read every approval — verify permissions before signing. Reject unlimited approvals
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
How big is the crypto scam problem?
  • $51 billion flowed to illicit crypto wallets in 2024 — CoinLedger
  • Pig butchering losses grew 40% year over year, now the fastest-growing fraud type
  • Only ~5% of victims report — your report helps shut down criminal networks
  • FBI recovered $1B+ in 2024 thanks to victim reports — FBI.gov

Sources: FBI · CoinLedger · WorldMetrics

Embed This Report

Share this threat intelligence on your website or blog