Skip to security report
wireconfirmation68c10a25442a3e13.blogspot.com favicon
Domain security and threat intelligence

wireconfirmation68c10a25442a3e13.blogspot.com

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

The screenshot shows a Blogger page at wireconfirmation68c10a25442a3e13.blogspot.com titled "Wire Confirmation." A single post dated Tuesday, July 23, 2019 displays an embedded image of a document-sharing prompt. The image includes the text "Here's the document that was shared with you," a notice that "This link will work for anyone," a PDF file labeled SCN22321, and a blue Open button, alongside Microsoft OneDrive branding. The post footer shows it was posted by Wire Confirmation with three comments.

Page title: “Wire Confirmation”

More about the sources
Recorded security signals

Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-01 13:25 UTC. Retrieved (as stored): 2026-11-10 21:57 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 13/92
Resolved IP
United States142.250.154.132Google LLC
First seen by PhishDestroy
2026-11-10
Page captures
open gallery
2026-11-10

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 wireconfirmation68c10a25442a3e13.blogspot.com on 2026-11-10. Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-01 13:25 UTC. Retrieved (as stored): 2026-11-10 21:57 UTC. Risk: critical (evidence score 99/100). Status: Last known active. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
13 / 92
Hosting
United States142.250.154.132Google LLC
Page captures
4

Cloudflare Radar capture · 2026-11-10 21:57 UTC · SHA-256 1b5f7b1c…5785d72

PhishDestroy analysis, reviewed version

The screenshot shows a Blogger page at wireconfirmation68c10a25442a3e13.blogspot.com titled "Wire Confirmation." A single post dated Tuesday, July 23, 2019 displays an embedded image of a document-sharing prompt. The image includes the text "Here's the document that was shared with you," a notice that "This link will work for anyone," a PDF file labeled SCN22321, and a blue Open button, alongside Microsoft OneDrive branding. The post footer shows it was posted by Wire Confirmation with three comments.

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

Source evidenceVirusTotal 13 / 92 5 sources

VirusTotal

13 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 16 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
ADMINUSLabs, alphaMountain.ai, CyRadar, ESET, Fortinet, Gridinsoft, Kaspersky, Lionic, SOCRadar, Sophos, VIPRE, Webroot, Xcitium Verdict Cloud
Observed at
2026-11-01 13:25:15
Checked at
2026-11-10 22:57:04
Fetched at
2026-11-10 21:57:05

URLScan

Page capture

SHA-256 a88d8269…51097f3

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

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

UUID
01a1c76e-61f0-7504-b994-1884871c6de4
Score
0
Malicious
✗
Result at
2026-11-12T04:30:27Z
Enriched at
2026-11-11T09:14:20Z
Source timestamps
Urlscan result at: 2026-11-12 05:30:27; Urlscan enriched at: 2026-11-11 10:14:20

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-10 22:09 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-10T22:09:36Z
Source timestamp
2026-11-10 23:09:36
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
wireconfirmation68c10a25442a3e13.blogspot.com: Wire Confirmation blog post
AI description
PhishDestroy records wireconfirmation68c10a25442a3e13.blogspot.com as a Blogger page titled Wire Confirmation showing a post with a shared document image.
AI summary
The screenshot shows a Blogger page at wireconfirmation68c10a25442a3e13.blogspot.com titled "Wire Confirmation." A single post dated Tuesday, July 23, 2019 displays an embedded image of a document-sharing prompt. The image includes the text "Here's the document that was shared with you," a notice that "This link will work for anyone," a PDF file labeled SCN22321, and a blue Open button, alongside Microsoft OneDrive branding. The post footer shows it was posted by Wire Confirmation with three comments. The stored VirusTotal domain result reports 13 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".
AI generated by
threat-v6-mimo
AI generated at
2026-11-10T21:59:45Z
Revision
455a0f47b725f1eae2a36ada40437e62856a655b03d5d0c80da221e5b163490b
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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
blogspot.com
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0
Average page size, bytes
6015

Crawler rules

User agents
  • Mediapartners-Google
  • *
Present
Yes
Sitemap URLs
  • https://wireconfirmation68c10a25442a3e13.blogspot.com/sitemap.xml

Sitemap

Present
Yes
URL count
1

Page title and metadata

Open Graph URL
https://wireconfirmation68c10a25442a3e13.blogspot.com/
Page title
Wire Confirmation
Open Graph title
Wire Confirmation
Generator
blogger
Canonical URL
https://wireconfirmation68c10a25442a3e13.blogspot.com/

Trackers

Requests
9
Observed services
  • Name
    Google Syndication
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google User Content
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    blogspot.com
    Company
    Google
    Country
    US
    Category
    Misc
    Requests
    5
  • Name
    Google+ Platform
    Company
    Google
    Country
    US
    Category
    Social Media
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://apis.google.com/js/platform.js
  • https://www.blogger.com/static/v1/widgets/2650890479-widgets.js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
2
TLS
18
Waiting
306
Connection
6
Download
0
Response time, ms
332

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
41461
CO₂, grams
0.0015
Cleaner than, %
41

DNS servers

Nameservers
  • IP address
    216.239.32.10
    Host
    ns1.google.com
  • IP address
    216.239.34.10
    Host
    ns2.google.com
  • IP address
    216.239.38.10
    Host
    ns4.google.com
  • IP address
    216.239.36.10
    Host
    ns3.google.com
DNS zone
blogspot.com

Location

IP address
2a00:1450:4001:c1f::84
ASN
15169
Organization
Google LLC
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Google Trust Services / WE2
Subject
misc-sni.blogspot.com

DNS records

A
  • 192.178.183.132
AAAA
  • 2a00:1450:4001:c1f::84
CNAME
  • blogspot.l.googleusercontent.com

DNSSEC

DS record
Yes
RRSIG
No
DNSKEY
Yes

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
1; mode=block
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a00:1450:4001:c1f::84
IP version
6

HTTP headers

Response headers
Server
GSE
Content-Type
text/html; charset=UTF-8
X-Content-Type-Options
nosniff
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 1; Domain: blogspot.com; Issuers: pki.goog
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Web archive observations
Last: 2023-11-25T18:13:38Z; First: 2020-03-26T03:51:37Z; Changes: 1; Days archived: 2; Scans per day: 0; Avg page bytes: 6015
Crawler rules
Agents: Mediapartners-Google, *; Present: ✓; Sitemaps: https://wireconfirmation68c10a25442a3e13.blogspot.com/sitemap.xml
Sitemap
Present: ✓; URL count: 1
Page title and metadata
Ogurl: https://wireconfirmation68c10a25442a3e13.blogspot.com/; Title: Wire Confirmation; Ogtitle: Wire Confirmation; Generator: blogger; Canonicalurl: https://wireconfirmation68c10a25442a3e13.blogspot.com/
Trackers
Requests: 9; Trackers: (Name: Google Syndication; Company: Google; Country: US; Category: Advertising; Requests: 1), (Name: Google APIs; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google User Content; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: blogspot.com; Company: Google; Country: US; Category: Misc; Requests: 5), (Name: Google+ Platform; Company: Google; Country: US; Category: Social Media; Requests: 1)
Forms and mixed content
No sri: https://apis.google.com/js/platform.js, https://www.blogger.com/static/v1/widgets/2650890479-widgets.js; Third party scripts: 2
Status
Up: ✓; Code: 302; Timings: DNS: 2; TLS: 18; Wait: 306; Connect: 6; Download: 0; Response ms: 332
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
Carbon
Bytes: 41461; Co2 grams: 0.0015; Cleaner than: 41
DNS server
NS: (IP: 216.239.32.10; Host: ns1.google.com), (IP: 216.239.34.10; Host: ns2.google.com), (IP: 216.239.38.10; Host: ns4.google.com), (IP: 216.239.36.10; Host: ns3.google.com); Zone: blogspot.com
Location
IP: 2a00:1450:4001:c1f::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: 192.178.183.132; Aaaa: 2a00:1450:4001:c1f::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:c1f::84; Family: 6
HTTP headers
Headers: Server: GSE; Content type: text/html; charset=UTF-8; X content type options: nosniff
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing

Questions about wireconfirmation68c10a25442a3e13.blogspot.com

Is wireconfirmation68c10a25442a3e13.blogspot.com legit?

PhishDestroy rates wireconfirmation68c10a25442a3e13.blogspot.com as critical risk (evidence score 99/100) from the recorded evidence; it was first recorded on 2026-11-10. Stored VirusTotal result: 13/92 engines flagged. Analysis time (as stored): 2026-11-01 13:25 UTC. Retrieved (as stored): 2026-11-10 21:57 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is wireconfirmation68c10a25442a3e13.blogspot.com safe to connect a wallet?

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

What should I do if I used wireconfirmation68c10a25442a3e13.blogspot.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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (4)

All capture links and hashes (4)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 94 report ↗
IP Reputation United States142.250.154.132 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 21 reports Port ScanHackingBrute-ForceSSH checked 2026-11-11 last reported
Platform provider blogspot.com
Hosting abuse contact abuse@google.com, network-abuse@google.com Google LLC · AS15169
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-10
DOM Analysisanalyzed 2026-11-10score 10/1001 brand signal
Submitted URLhttp://wireconfirmation68c10a25442a3e13.blogspot.com/
Favicon Hash
Observed page title
Wire Confirmation
Automated brand references
Google
TLS Certificate
Issued by Google Trust Services / WE2 · stored validity ends in 64 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States142.250.154.132
Network ASN
AS15169
AS name
GOOGLE - Google LLC, US
Organization
Google LLC
Observed location
United StatesMountain View, US
Server header
GSE

Nameservers 1

  • ns4.google.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE2
Valid from
2026-11-03 08:28:12
Valid until
2027-01-26 08:28:11
Hostname match
Yes
Validity
Within stored validity dates
Collection time
2026-11-10 23:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprint410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27
Certificate names · 139 SANs
  • *.blogspot.ae
  • *.blogspot.al
  • *.blogspot.am
  • *.blogspot.ba
  • *.blogspot.be
  • *.blogspot.bg
  • *.blogspot.ca
  • *.blogspot.ch
  • *.blogspot.cl
  • *.blogspot.co.at
  • *.blogspot.co.id
  • *.blogspot.co.il
  • *.blogspot.co.ke
  • *.blogspot.co.nz
  • *.blogspot.co.uk
  • *.blogspot.co.za
  • *.blogspot.com
  • *.blogspot.com.ar
  • *.blogspot.com.au
  • *.blogspot.com.br
  • *.blogspot.com.by
  • *.blogspot.com.co
  • *.blogspot.com.cy
  • *.blogspot.com.ee
  • *.blogspot.com.eg
  • *.blogspot.com.es
  • *.blogspot.com.mt
  • *.blogspot.com.ng
  • *.blogspot.com.tr
  • *.blogspot.com.uy
  • *.blogspot.cz
  • *.blogspot.de
  • *.blogspot.dk
  • *.blogspot.fi
  • *.blogspot.fr
  • *.blogspot.gr
  • *.blogspot.hk
  • *.blogspot.hr
  • *.blogspot.hu
  • *.blogspot.ie
  • *.blogspot.in
  • *.blogspot.is
  • *.blogspot.it
  • *.blogspot.jp
  • *.blogspot.kr
  • *.blogspot.li
  • *.blogspot.lt
  • *.blogspot.lu
  • *.blogspot.md
  • *.blogspot.mk
  • *.blogspot.mx
  • *.blogspot.my
  • *.blogspot.nl
  • *.blogspot.no
  • *.blogspot.pe
  • *.blogspot.pt
  • *.blogspot.qa
  • *.blogspot.ro
  • *.blogspot.rs
  • *.blogspot.ru
  • *.blogspot.se
  • *.blogspot.sg
  • *.blogspot.si
  • *.blogspot.sk
  • *.blogspot.sn
  • *.blogspot.tw
  • *.blogspot.ug
  • *.blogspot.vn
  • *.bp.blogspot.com
  • blogspot.ae
  • blogspot.al
  • blogspot.am
  • blogspot.ba
  • blogspot.be
  • blogspot.bg
  • blogspot.ca
  • blogspot.ch
  • blogspot.cl
  • blogspot.co.at
  • blogspot.co.id
  • blogspot.co.il
  • blogspot.co.ke
  • blogspot.co.nz
  • blogspot.co.uk
  • blogspot.co.za
  • blogspot.com
  • blogspot.com.ar
  • blogspot.com.au
  • blogspot.com.br
  • blogspot.com.by
  • blogspot.com.co
  • blogspot.com.cy
  • blogspot.com.ee
  • blogspot.com.eg
  • blogspot.com.es
  • blogspot.com.mt
  • blogspot.com.ng
  • blogspot.com.tr
  • blogspot.com.uy
  • blogspot.cz
  • blogspot.de
  • blogspot.dk
  • blogspot.fi
  • blogspot.fr
  • blogspot.gr
  • blogspot.hk
  • blogspot.hr
  • blogspot.hu
  • blogspot.ie
  • blogspot.in
  • blogspot.is
  • blogspot.it
  • blogspot.jp
  • blogspot.kr
  • blogspot.li
  • blogspot.lt
  • blogspot.lu
  • blogspot.md
  • blogspot.mk
  • blogspot.mx
  • blogspot.my
  • blogspot.nl
  • blogspot.no
  • blogspot.pe
  • blogspot.pt
  • blogspot.qa
  • blogspot.ro
  • blogspot.rs
  • blogspot.ru
  • blogspot.se
  • blogspot.sg
  • blogspot.si
  • blogspot.sk
  • blogspot.sn
  • blogspot.tw
  • blogspot.ug
  • blogspot.vn
  • bp.blogspot.com
  • misc-sni.blogspot.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:19 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-22 11:19 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:19 UTC last content: 2026-11-22 11:19 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.
Technologies · 6 identified
Open complete records

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
ESET
VIPRE
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
Gridinsoft
ADMINUSLabs
alphaMountain.ai
Xcitium Verdict Cloud
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

All stored data99
Open complete records

Captured network requests

Network requests: 8 SHA-256 hashes: 8 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-10 21:53 UTC.

Open this scan on URLScan 01a1c76e-61f0-7504-b994-1884871c6de4 ↗

Stored observation history12

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

    Serving page content

    page content returned

  2. Availability monitor · Recorded state

    Serving page content

    page content returned

  3. Availability monitor · Recorded state

    Serving page content

    page content returned

  4. Availability monitor · Recorded state

    Serving page content

    page content returned

  5. Availability monitor · Recorded state

    Serving page content

    page content returned

Earlier observations 7
  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Availability monitor · Recorded state

    Serving page content

    page content returned

  3. Availability monitor · Recorded state

    Serving page content

    page content returned

  4. Availability monitor · Recorded state

    Serving page content

    page content returned

  5. Availability monitor · Recorded state

    Serving page content

    page content returned

  6. Availability monitor · Recorded state

    Serving page content

    page content returned

  7. Domain monitor · First collection record

    Reachable

All retained availability observations40
Open complete records

Threat Response Pipeline

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

Recorded events: 9. 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
    wireconfirmation68c10a25442a3e13.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+9588 d 15 h
  3. Added to PhishDestroy+9 d 8 h
  1. Cloudflare Radar

    Phishing

    +8 min
  2. Added to PhishDestroy

    wireconfirmation68c10a25442a3e13.blogspot.com

    same minute
  3. URLScan

    Page captured

    +9 d 8 h
  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.

wireconfirmation68c10a25442a3e13.blogspot.com

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 wireconfirmation68c10a25442a3e13.blogspot.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)
  • 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/wireconfirmation68c10a25442a3e13.blogspot.com"
  title="PhishDestroy threat report for wireconfirmation68c10a25442a3e13.blogspot.com"
  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>