Skip to security report
instagram030.github.io favicon
Domain security and threat intelligence

instagram030.github.io

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

On 2026-11-15, the page displayed a mobile-themed container branded with TikTok elements, featuring a central video player graphic with a play button overlay. Below the video area, text in Cyrillic announces a game bug related to Brawl Stars, accompanied by interaction metrics such as likes and comments, along with a prominent pink call-to-action button to open the content in TikTok.

More about the sources
Recorded security signals

Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-13 06:14 UTC. Retrieved (as stored): 2026-11-15 20:10 UTC. Listed by external blocklists: Phishunt, PhishFeed. Use caution — do not enter credentials or personal information.

VirusTotal detections: 13/92 Stored blocklist matches: 2 Google Safe Browsing: threat flag recorded
Resolved IP
United States185.199.109.153GitHub, Inc · CDN
First seen by PhishDestroy
2026-11-15
URLScan
engine verdict · score 97
Page captures
open gallery
2026-11-15 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded instagram030.github.io on 2026-11-15. Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-13 06:14 UTC. Retrieved (as stored): 2026-11-15 20:10 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Status: HTTP 404 · Content unavailable. Hosting: Fastly, Inc. Listed by external blocklists: Phishunt, PhishFeed. Do not enter credentials or connect a wallet.

Critical
Status
HTTP 404 · Content unavailable
VirusTotal
13 / 92
Blocklist matches
2 external + PhishDestroy list
Hosting
United States185.199.109.153GitHub, Inc · CDN
Page captures
9

URLScan capture · 2026-11-15 20:07 UTC · SHA-256 6f7e1d5c…64db5b2

PhishDestroy analysis, reviewed version

On 2026-11-15, the page displayed a mobile-themed container branded with TikTok elements, featuring a central video player graphic with a play button overlay. Below the video area, text in Cyrillic announces a game bug related to Brawl Stars, accompanied by interaction metrics such as likes and comments, along with a prominent pink call-to-action button to open the content in TikTok.

The stored VirusTotal domain result reports 13 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".

Source evidenceVirusTotal 13 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

13 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
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
Result state
observed
Numerator
13
Denominator
92
Vendors
alphaMountain.ai, DNS8, ESET, Emsisoft, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, MalwareURL, Netcraft, SOCRadar, Sophos, Webroot
Observed at
2026-11-13 06:14:27
Checked at
2026-11-15 21:10:53
Fetched at
2026-11-15 20:10:54

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Page capture

SHA-256 f1908856…0d36c69

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record · 2026-11-16 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1e0d2-3988-728b-970e-95d399ffc6c2
Score
0
Malicious
✗
Result at
2026-11-16T04:30:26Z
Enriched at
2026-11-16T09:12:02Z
Source timestamps
Urlscan result at: 2026-11-16 05:30:26; Urlscan enriched at: 2026-11-16 10:12:02

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-16 03:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
10
Analyzed at
2026-11-16T03:20:11Z
Source timestamp
2026-11-16 04:20:11
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
instagram030.github.io Mobile-Themed Video Page
AI description
PhishDestroy analyzes instagram030.github.io, presenting a mobile-themed interface featuring a video player and promotional text.
AI summary
On 2026-11-15, the page displayed a mobile-themed container branded with TikTok elements, featuring a central video player graphic with a play button overlay. Below the video area, text in Cyrillic announces a game bug related to Brawl Stars, accompanied by interaction metrics such as likes and comments, along with a prominent pink call-to-action button to open the content in TikTok. The stored VirusTotal domain result reports 13 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
AI generated by
threat-v6-gemini
AI generated at
2026-11-15T20:39:25Z
Revision
4024237a2f5caa64dc9bd205f4f44fbe4f8ea812cc8123ff9a2ebac857766509
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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: 16 fields

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
instagram030.github.io
Allowed issuers
  • digicert.com
  • letsencrypt.org
  • sectigo.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
DNS zone
github.io

Page quality

Layout shift (CLS)
0
SEO score
82
Speed Index, s
0.79
First Contentful Paint (FCP), s
0.79
Largest Contentful Paint (LCP), s
0.79
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
55
Best practices score
92

Location

IP address
2606:50c0:8001::153
ASN
54113
Organization
Fastly, Inc.
City
San Francisco
Country
US

TLS certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Key size, bits
2048
Certificate chain
  • *.github.io
  • YR1
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR1
Serial
06A65E5D3279BA564A4DE74EB5D64478DBB8
SHA-256
f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Subject
*.github.io
Valid until
Valid from

DNS records

A
  • 185.199.108.153
  • 185.199.109.153
  • 185.199.110.153
  • 185.199.111.153
AAAA
  • 2606:50c0:8000::153
  • 2606:50c0:8003::153
  • 2606:50c0:8001::153
  • 2606:50c0:8002::153

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:50c0:8001::153
IP version
6

TLS configuration test

Grades
  • B
Status
READY

HTTP headers

Response headers
Server
GitHub.com
Content-Type
text/html; charset=utf-8
Content-Security-Policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Via
1.1 varnish
X-Cache
HIT
X-Cache-Hits
3
X-Served-By
cache-fra-etou8220141-FRA
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 6; Domain: instagram030.github.io; Issuers: digicert.com, letsencrypt.org, sectigo.com
Protective DNS results
Resolvers: 12; Blocked count: 0
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
DNS server
NS: (IP: 205.251.193.137; Host: ns-393.awsdns-49.com), (IP: 205.251.194.180; Host: ns-692.awsdns-22.net), (IP: 198.51.44.5; Host: dns1.p05.nsone.net), (IP: 198.51.45.5; Host: dns2.p05.nsone.net), (IP: 198.51.44.69; Host: dns3.p05.nsone.net), (IP: 198.51.45.69; Host: dns4.p05.nsone.net), (IP: 205.251.197.59; Host: ns-1339.awsdns-39.org), (IP: 205.251.198.86; Host: ns-1622.awsdns-10.co.uk); Zone: github.io
Quality
Cls: 0; Seo: 82; Si s: 0.79; Fcp s: 0.79; Lcp s: 0.79; Tbt ms: 0; Performance: 100; Accessibility: 55; Best practices: 92
Location
IP: 2606:50c0:8001::153; ASN: 54113; Org: Fastly, Inc.; City: San Francisco; Country: US
SSL
San: *.github.com, *.github.io, *.githubusercontent.com, github.com, github.io, githubusercontent.com; Bits: 2048; Chain: *.github.io, YR1, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR1; Serial: 06A65E5D3279BA564A4DE74EB5D64478DBB8; SHA256: f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856; Subject: *.github.io; Valid to: 2026-12-29T23:44:45Z; Valid from: 2026-09-30T23:44:46Z
DNS records
A: 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153; Aaaa: 2606:50c0:8000::153, 2606:50c0:8003::153, 2606:50c0:8001::153, 2606:50c0:8002::153
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2606:50c0:8001::153; Family: 6
TLS labs
Grades: B; Status: READY
HTTP headers
Headers: Server: GitHub.com; Content type: text/html; charset=utf-8; Content security policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Via: 1.1 varnish; X cache: HIT; X cache hits: 3; X served by: cache-fra-etou8220141-FRA

Questions about instagram030.github.io

Is instagram030.github.io legit?

PhishDestroy rates instagram030.github.io as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-11-15. Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-13 06:14 UTC. Retrieved (as stored): 2026-11-15 20:10 UTC. Google Safe Browsing flags it. Listed by external blocklists: Phishunt, PhishFeed. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is instagram030.github.io safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on instagram030.github.io. A confirmed blockchain transaction cannot be reversed.

What should I do if I used instagram030.github.io?

  • 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.

Explore

Blocklist matches2 external + PhishDestroy list · PhishDestroy · Phishunt · PhishFeed 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source
PhishFeed Listed View source

Last checked

Page captures (9)

All capture links and hashes (9)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
Google Safe Browsing Flagged Social engineering checked 2026-11-22
IP Context United States185.199.109.153 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider github.io
Abuse contactabuse@github.com
HTTP Status404 Not Found
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-15
DOM Analysisanalyzed 2026-11-16score 10/1002 brand signals
Submitted URLhttp://instagram030.github.io/-
Favicon Hash
Observed page title
Site not found · GitHub Pages
Automated brand references
Google TikTok
TLS Certificate
Issued by YR1 · stored validity ends in 37 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States185.199.109.153
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
GitHub, Inc
Observed location
United StatesSan Francisco, US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • ns-692.awsdns-22.net

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com

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

Latest Classified Outcome 2026-11-21 11:11 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale
Latest HTTP observation Inactive Http No Content 70% 2026-11-21 11:11 UTC
RDAP registration
Observed timeline last reachable: 2026-11-15 20:08 UTC current episode first observed: 2026-11-16 00:09 UTC observed RIP window: 2026-11-15 20:08 UTC → 2026-11-16 00:09 UTC · 4.02h midpoint estimate ≈ 2026-11-15 22:09 UTC · precision high · basis bounded
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.
Technologies · 3 identified
Open complete records

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
DNS8
ESET
G-Data
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
Gridinsoft
MalwareURL
alphaMountain.ai
Google Safe Browsing
PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of instagram030.github.io ·

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

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
4.02
Estimate basis
Bounded by observations
Estimate precision
High

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data110
Open complete records

Captured network requests

Network requests: 4 SHA-256 hashes: 4 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-15 20:09 UTC.

Open this scan on URLScan 01a1e0d2-3988-728b-970e-95d399ffc6c2 ↗

Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Domain monitor · First collection record

    Reachable

All retained availability observations15
Open complete records

Threat Response Pipeline

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

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
  • Threat Ingested
    instagram030.github.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Automated brand label: Instagram · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+4997 d 10 h
  3. Added to PhishDestroy+61 h 53 min
  1. Google Safe Browsing

    Threat flag recorded

    +6 d 8 h
  2. Added to PhishDestroy

    instagram030.github.io

    same minute
  3. URLScan

    Page captured

    +61 h 53 min
  4. 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
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.

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.

instagram030.github.io

Evidence & External Reports

Deep Analysis

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

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • 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 instagram030.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)
  • 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

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.

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.

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/instagram030.github.io"
  title="PhishDestroy threat report for instagram030.github.io"
  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>