Google Safe Browsing
Threat flag recorded
Open reportOn 2026-11-09, minecrfatco.blogspot.com displayed a dark-themed page with a pixel-style MINECRAFT logo above a centered panel. The panel instructs visitors to enter their Username or ID and select a platform, with a text field labeled Username/ID and four icon buttons for Apple, Android, a game controller, and Windows, followed by a CONTINUE button. The page presents only this single entry form against a plain dark background, with no other visible sections or links.
Page title: “Minecraft Coins Generator”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Cloudflare Radar capture · 2026-11-09 13:43 UTC · SHA-256 2d8f7a44…f52e5e8
PhishDestroy analysis, reviewed version
On 2026-11-09, minecrfatco.blogspot.com displayed a dark-themed page with a pixel-style MINECRAFT logo above a centered panel. The panel instructs visitors to enter their Username or ID and select a platform, with a text field labeled Username/ID and four icon buttons for Apple, Android, a game controller, and Windows, followed by a CONTINUE button. The page presents only this single entry form against a plain dark background, with no other visible sections or links.
The stored VirusTotal domain result reports 0 detections out of 92 engines.
Threat flag recorded
Open reportScan report
Open reportPage capture
SHA-256 6069a3de…51fc64f
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
10 / 100 · heuristic score · 2 brand references · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Caa records | Count: 1; Domain: blogspot.com; Issuers: pki.goog |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-11-09T13:09:10Z; First: 2026-11-09T13:09:10Z; Changes: 0; Days archived: 1; Avg page bytes: 11553 |
| Trackers | Requests: 16; Trackers: (Name: Amazon CloudFront; Company: Amazon; Country: US; Category: Hosting; Requests: 11), (Name: Google APIs; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Analytics; Company: Google; Country: US; Category: Site Analytics; Requests: 1), (Name: Sentry; Company: Sentry; Country: US; Category: Utilities; Requests: 1) |
| Forms and mixed content | No sri: https://d9qn9uafc7mxn.cloudfront.net/89adedd.js, https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js; Third party scripts: 3 |
| Status | Up: ✓; Code: 302; Timings: DNS: 6; TLS: 26; Wait: 401; Connect: 9; Download: 0; Response ms: 442 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443 |
| DNS server | NS: (IP: 216.239.34.10; Host: ns2.google.com), (IP: 216.239.32.10; Host: ns1.google.com), (IP: 216.239.36.10; Host: ns3.google.com), (IP: 216.239.38.10; Host: ns4.google.com); Zone: blogspot.com |
| Location | IP: 2a00:1450:4001:c13::84; ASN: 15169; Org: Google LLC; City: Frankfurt am Main; Country: DE |
| SSL | Issuer: Google Trust Services / WE2; Subject: misc-sni.blogspot.com |
| DNS records | A: 142.251.127.132; Aaaa: 2a00:1450:4001:c13::84; Cname: blogspot.l.googleusercontent.com |
| Dnssec | Ds: ✓; Rrsig: ✗; Dnskey: ✓ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: 1; mode=block; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 2a00:1450:4001:c13::84; Family: 6 |
| Redirects | Chain: https://minecrfatco.blogspot.com |
| Tech stack | Technologies: Blogger, Sentry, Python, Java, OpenGSE, Google Hosted Libraries, jQuery, Google Analytics, Cloudflare Rocket Loader, CPABuild, Open Graph, HTTP/3 |
| HTTP headers | Headers: Server: GSE; Content type: text/html; charset=UTF-8; X content type options: nosniff |
PhishDestroy rates minecrfatco.blogspot.com as critical risk (evidence score 80/100) from the recorded evidence; it was first recorded on 2026-11-09. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on minecrfatco.blogspot.com. A confirmed blockchain transaction cannot be reversed.
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.
ns4.google.comLocation describes the IP network.
misc-sni.blogspot.comblogspot.ae*.blogspot.aeblogspot.al*.blogspot.alblogspot.am*.blogspot.amblogspot.ba*.blogspot.bablogspot.beSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
No phishing content was served at the latest check.
Google PageSpeed Insights — mobile performance audit of minecrfatco.blogspot.com ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://minecrfatco.blogspot.com/Content-Type: text/html; charset=UTF-8Cache-Control: private, max-age=0Content-Encoding: gzipServer: GSEa1495da3cf3db37bf105a12658636ff628fee7b73975b9200049af7747e60b1fh3=":443"; ma=2592000,h3-29=":443"; ma=2592000private, max-age=0gzipupgrade-insecure-requestsdefault-src https: blob: data: 'unsafe-inline' 'unsafe-eval'; report-to blogspot; report-uri https://www.blogger.com/cspreporttext/html; charset=UTF-8Mon, 09 Nov 2026 13:07:59 GMTW/"fea4bc77eaa5ce32ff7cd03fd020bc5fb609f2f0231be10bed04db9e01232432"Mon, 09 Nov 2026 13:07:59 GMTThu, 29 Aug 2024 19:01:53 GMT{"group":"blogspot","max_age":2592000,"endpoints":[{"url":"https://www.blogger.com/cspreport"}]}GSEchunkednosniff1; mode=blockValues 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.
Network requests: 28 SHA-256 hashes: 28 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-09 13:13 UTC.
Open this scan on URLScan 01a1c06c-3469-70bc-b32f-368407a2524a ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
minecrfatco.blogspot.com Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
minecrfatco.blogspot.com)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.