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

naemmurshed.github.io

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

PhishDestroy records that naemmurshed.github.io displayed a page titled Minecraft Coins Generator, offering coin packages and a username entry form on 2026-10-23.

Page title: “Minecraft Coins Generator”

More about the sources

Use caution — do not enter credentials or personal information.

Stored PhishDestroy threat listing
Resolved IP
United States185.199.108.153GitHub, Inc · CDN
First seen by PhishDestroy
2026-10-23
Page captures
open gallery
2026-10-23 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

Critical
Status
HTTP 404 · Content unavailable
Scam type (automated label)
Impersonation
Hosting
United States185.199.108.153GitHub, Inc · CDN
Page captures
4

URLScan capture · 2026-10-23 00:12 UTC · SHA-256 3778d4ff…a64acc7

PhishDestroy analysis, reviewed version

On 2026-10-23, naemmurshed.github.io displayed a page titled "Minecraft Coins Generator" set against a Minecraft-style landscape background with the Minecraft logo at the top. The page invites visitors to claim a coins package by filling out a form, noting that the generator can only be used once every 24 hours.

The form asks for a Minecraft Games Username in a text field labeled "username or id," with instructions to enter the exact username with proper capitalization. Below that, three selectable coin packages are shown: 1,700 Coins, 4,500 Coins, and 10,000 Coins, followed by a "Generate Now" button. A lower panel shows a progress bar with steps labeled generation and Verification, alongside a "Generator Chatroom" section.

Source evidence 3 sources

URLScan

Page capture

SHA-256 67d7b23e…d229386

Open report
URLScanOriginal source recordObserved: 21 fields
Separate monitor record · 2026-10-23 03:30 UTC

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

UUID
01a16619-d68b-77f4-95ef-d2df341c9768
Score
0
Malicious
✗
Result at
2026-10-23T03:30:23Z
Enriched at
2026-10-23T08:16:58Z
Source timestamps
Urlscan result at: 2026-10-23 05:30:23; Urlscan enriched at: 2026-10-23 10:16:58

PhishDestroy DOM

76 / 100 · heuristic score · 5 brand references · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-10-23 02: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-10-23T02:20:31Z
Source timestamp
2026-10-23 04:20:31
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
naemmurshed.github.io: Recorded Minecraft Coins Generator Page
AI description
PhishDestroy records that naemmurshed.github.io displayed a page titled Minecraft Coins Generator, offering coin packages and a username entry form on 2026-10-23.
AI summary
On 2026-10-23, naemmurshed.github.io displayed a page titled "Minecraft Coins Generator" set against a Minecraft-style landscape background with the Minecraft logo at the top. The page invites visitors to claim a coins package by filling out a form, noting that the generator can only be used once every 24 hours. The form asks for a Minecraft Games Username in a text field labeled "username or id," with instructions to enter the exact username with proper capitalization. Below that, three selectable coin packages are shown: 1,700 Coins, 4,500 Coins, and 10,000 Coins, followed by a "Generate Now" button. A lower panel shows a progress bar with steps labeled generation and Verification, alongside a "Generator Chatroom" section.
AI generated by
threat-v6-mimo
AI generated at
2026-11-04T08:34:08Z
Revision
15ed317252f445f3d016bd296d8e16e5896691c1c95124b0e77ff4229b0b0617
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
VirusTotalOriginal source recordObserved: 13 fields
Open complete records
Website checksOriginal source recordRetrieved: 14 fields

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
naemmurshed.github.io
Allowed issuers
  • letsencrypt.org
  • sectigo.com
  • digicert.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
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
DNS zone
github.io

Location

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

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
*.github.io

DNS records

A
  • 185.199.110.153
  • 185.199.108.153
  • 185.199.111.153
  • 185.199.109.153
AAAA
  • 2606:50c0:8002::153
  • 2606:50c0:8003::153
  • 2606:50c0:8000::153
  • 2606:50c0:8001::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:8003::153
IP version
6

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
4
X-Served-By
cache-par-lfpg1960030-PAR
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 6; Domain: naemmurshed.github.io; Issuers: letsencrypt.org, sectigo.com, digicert.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: 198.51.45.69; Host: dns4.p05.nsone.net), (IP: 205.251.193.137; Host: ns-393.awsdns-49.com), (IP: 205.251.197.59; Host: ns-1339.awsdns-39.org), (IP: 205.251.194.180; Host: ns-692.awsdns-22.net), (IP: 205.251.198.86; Host: ns-1622.awsdns-10.co.uk), (IP: 198.51.44.5; Host: dns1.p05.nsone.net), (IP: 198.51.44.69; Host: dns3.p05.nsone.net), (IP: 198.51.45.5; Host: dns2.p05.nsone.net); Zone: github.io
Location
IP: 2606:50c0:8002::153; ASN: 54113; Org: Fastly, Inc.; City: San Francisco; Country: US
SSL
Issuer: Let's Encrypt / YR1; Subject: *.github.io
DNS records
A: 185.199.110.153, 185.199.108.153, 185.199.111.153, 185.199.109.153; Aaaa: 2606:50c0:8002::153, 2606:50c0:8003::153, 2606:50c0:8000::153, 2606:50c0:8001::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:8003::153; Family: 6
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: 4; X served by: cache-par-lfpg1960030-PAR

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (4)

All capture links and hashes (4)
naemmurshed.github.io: caution — 5/92 VirusTotal engines. PhishDestroy risk score 76/100 (critical).
Social preview card naemmurshed.github.io: caution — 5/92 VirusTotal engines. PhishDestroy risk score 76/100 (critical). v 8eb5ab8315a0

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 95 report ↗
IP Context United States185.199.108.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-10-23
DOM Analysisanalyzed 2026-10-23score 76/1005 brand signals
Submitted URLhttps://naemmurshed.github.io/Minecraft-Coins-Generator/
Favicon Hash
Observed page title
Minecraft Coins Generator
Automated brand references
Facebook Minecraft Reddit Robux Twitch
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.108.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-22 11:41 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-22 11:41 UTC
RDAP registration
Observed timeline last reachable: 2026-10-23 00:13 UTC current episode first observed: 2026-10-23 10:00 UTC observed RIP window: 2026-10-23 00:13 UTC → 2026-10-23 10:00 UTC · 9.78h midpoint estimate ≈ 2026-10-23 05:07 UTC · precision medium · 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.
Registration & observation details8

Availability observations

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

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

All stored data102
Open complete records

Captured network requests

Network requests: 26 SHA-256 hashes: 23 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-10-29 03:01 UTC.

Open this scan on URLScan 01a16619-d68b-77f4-95ef-d2df341c9768 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Minecraft Coins Generator
Crawler
Site not found · GitHub Pages
naemmurshed.github.io
Stored observation history6

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. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  3. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  4. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  5. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

Earlier observations 1
  1. Domain monitor · First collection record

    Reachable

All retained availability observations98
Open complete records

Threat Response Pipeline

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

Recorded events: 7. 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
    naemmurshed.github.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Automated brand label: Minecraft · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

2 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+4976 d 4 h
  1. Added to PhishDestroy

    naemmurshed.github.io

    same minute
  2. URLScan

    Page captured

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

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