Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 3. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
xapp-folks-finance.web.app favicon

xapp-folks-finance.web.app

In short

PhishDestroy records the captured Folks Finance lending page at xapp-folks-finance.web.app, showing wallet connection and market listings.

“Folks Finance”

Registrar
United StatesGoogle Domains
Resolved IP
United States199.36.158.100Fastly, Inc. · CDN
First observed
Oct 22, 2026
PhishDestroy assessment Critical
84/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 3/92 Stored blocklist matches: 3
VirusTotal
engine detections ·
Blocklist matches
MetaMask, ScamSniffer, SEAL
URLScan
engine verdict · score 100
Page captures
open gallery
Oct 22, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records the captured Folks Finance lending page at xapp-folks-finance.web.app, showing wallet connection and market listings.

Critical
Status
Last known active
VirusTotal
3 / 92
Blocklist matches
3
Scam type (automated label)
Crypto Drainer
Hosting
United States199.36.158.100Fastly, Inc. · CDN
Registrar
United StatesGoogle Domains
Page captures
3

PhishDestroy analysis, reviewed version

The captured page presents itself as Folks Finance, a cross-chain lending interface whose Get Started panel asks visitors to connect a wallet, then create an account, then start using the service. A Connect Wallet button sits beside those steps, and a Markets table below lists tokens with deposited and borrowed totals alongside deposit and borrow rates. A banner across the top announces that the website will shut down on March 31, 2027 and directs users to withdraw funds, linking to a transition plan.

The stored VirusTotal result reports 6 detections out of 92 engines.

Source evidenceVirusTotal 3 / 92 8 sources

VirusTotal

3 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
3
Suspicious
0
Undetected
34

Vendor labels

VIPRE
malware
ChainPatrol
malicious
alphaMountain.ai
malicious

Reputation score

0

Categories

alphaMountain.ai
Hosting, Malicious (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    AAAA
    Value
    2620:0:890::100
  • TTL, seconds
    21600
    Type
    A
    Value
    199.36.158.100

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • web.app
  • *.web.app
Issuer
Google Trust Services / WR4
Serial
e26d762a101120cd12a8f68d86c31d05
SHA-256
7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Subject
web.app
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.googledomains.com
  • ns2.googledomains.com
  • ns3.googledomains.com
  • ns4.googledomains.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "VIPRE": "malware",
    "ChainPatrol": "malicious",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Hosting, Malicious (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2019-01-08T22:05:04Z
Expires
2026-01-08T22:05:04Z
Updated
2024-12-12T10:14:49Z
First seen
2026-10-10T17:34:28Z
DNS records
[
    {
        "ttl": 21600,
        "type": "AAAA",
        "value": "2620:0:890::100"
    },
    {
        "ttl": 21600,
        "type": "A",
        "value": "199.36.158.100"
    }
]
Dns at
2026-10-11T08:30:02Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "issuer": "Google Trust Services / WR4",
    "serial": "e26d762a101120cd12a8f68d86c31d05",
    "sha256": "7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095",
    "subject": "web.app",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2019-01-08T22:05:04Z",
    "updated": "2024-12-12T10:14:49Z",
    "expires": "2026-01-08T22:05:04Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.googledomains.com",
        "ns2.googledomains.com",
        "ns3.googledomains.com",
        "ns4.googledomains.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 3 malicious + 0 suspicious / 92 · 2026-10-11 08:29:49 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-11T08:29:49Z
fetched_at
2026-10-22T20:38:29Z
stats
{"timeout":0,"harmless":55,"malicious":3,"suspicious":0,"undetected":34}

URLScan

Malicious · engine verdict · score 100

SHA-256 2b60900c86fc52136d9a2343683a71c95e68dd0a030a4a5426ea3de19499dc4b

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1654c-da4e-763f-a949-8ce5fbcc7e8e

Final URL

https://xapp-folks-finance.web.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://xapp-folks-finance.web.app/
    From
    http://xapp-folks-finance.web.app/
    Status
    307

IP address

199.36.158.100

Contacted IP addresses

  • 199.36.158.100

Autonomous systems (ASN)

  • 54113

Server countries

  • US

Linked domains

  • forum.folks.finance
  • xapp.folks.finance

Document hash

a8110b5da8b49573c660baf4937dcb4ea4e854240375f1660ae4817363896d3f

Script hashes

  • d789db1f10a46f1d2579af77ed3fe5d8e71c2e3b0ffcf6edb48b72bf094c09ae

TLS session and certificate

Subject alternative names
  • web.app
  • *.web.app
Cipher
AES_128_GCM
Issuer
WR4
Subject
web.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

11

Registered domain age, days

11

Certificate age, days

29

Certificate validity, days

89

Page requests

38

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1654c-da4e-763f-a949-8ce5fbcc7e8e
Final url
https://xapp-folks-finance.web.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://xapp-folks-finance.web.app/",
        "from": "http://xapp-folks-finance.web.app/",
        "status": 307
    }
]
Ip
199.36.158.100
Contacted IP addresses
[
    "199.36.158.100"
]
Asns
[
    "54113"
]
Countries
[
    "US"
]
Linked domains
[
    "forum.folks.finance",
    "xapp.folks.finance"
]
Document hash
a8110b5da8b49573c660baf4937dcb4ea4e854240375f1660ae4817363896d3f
Script hashes
[
    "d789db1f10a46f1d2579af77ed3fe5d8e71c2e3b0ffcf6edb48b72bf094c09ae"
]
Tls
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR4",
    "subject": "web.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Domain age days
11
Apex age days
11
Tls age days
29
Tls valid days
89
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
}
Separate monitor record · 2026-10-23 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1654c-da4e-763f-a949-8ce5fbcc7e8e
score
0
malicious
false
result_at
2026-10-23T03:30:42Z
enriched_at
2026-10-23T08:21:40Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:42","urlscan_enriched_at":"2026-10-23 10:21:40"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

20 / 100 · heuristic score · 9 brand references · 1 classification

Open report
Separate monitor score · 20 / 100 · 2026-10-22T22:20:26Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
20
analyzed_at
2026-10-22T22:20:26Z
source_timestamp
2026-10-23 00:20:26
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
xapp-folks-finance.web.app Folks Finance lending dashboard
ai_description
PhishDestroy records the captured Folks Finance lending page at xapp-folks-finance.web.app, showing wallet connection and market listings.
ai_summary
The captured page presents itself as Folks Finance, a cross-chain lending interface whose Get Started panel asks visitors to connect a wallet, then create an account, then start using the service. A Connect Wallet button sits beside those steps, and a Markets table below lists tokens with deposited and borrowed totals alongside deposit and borrow rates. A banner across the top announces that the website will shut down on March 31, 2027 and directs users to withdraw funds, linking to a transition plan. The stored VirusTotal result reports 6 detections out of 92 engines.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 03:33:07
revision
a98c7cd193ce56afde9da5b9fe9477f5dac520b2e2ecaded69c2f3df5abd556a
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
web.app
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Open Graph URL
https://xapp.folks.finance
Page title
Folks Finance
Open Graph type
website
Open Graph image
https://xapp.folks.finance/opengraph-image
Open Graph title
Folks Finance
Open Graph site name
Folks Finance
Description
Lend and borrow crypto with ease across multiple chains. Powered by Chainlink, Wormhole, and Circle messaging layers technology.
Twitter card
summary_large_image
Twitter account
@FolksFinance
Canonical URL
https://xapp.folks.finance/
Open Graph description
Lend and borrow crypto with ease across multiple chains. Powered by Chainlink, Wormhole, and Circle messaging layers technology.
Twitter Creator
@FolksFinance

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
14
TLS
30
Waiting
21
Connection
18
Download
74
Response time, ms
157

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

Carbon estimate

Bytes
367716
CO₂, grams
0.0134
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    216.239.38.99
    Host
    ns4.googledomains.com
  • IP address
    216.239.34.99
    Host
    ns2.googledomains.com
  • IP address
    216.239.32.99
    Host
    ns1.googledomains.com
  • IP address
    216.239.36.99
    Host
    ns3.googledomains.com
DNS zone
web.app

Location

IP address
2620:0:890::100
ASN
54113
Organization
Fastly, Inc.
City
Mountain View
Country
US

TLS certificate

Issuer
Google Trust Services / WR4
Subject
web.app

DNS records

A
  • 199.36.158.100
AAAA
  • 2620:0:890::100

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31556926; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

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
No
Strict-Transport-Security
max-age=31556926; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2620:0:890::100
IP version
6

Redirects

Redirect chain
  • https://xapp-folks-finance.web.app

Social profiles

Profiles
  • https://x.com/FolksFinance

Page links

External link addresses
  • https://forum.folks.finance/t/xchain-transition-plan-moving-to-the-next-product-evolution/2063
  • https://xapp.folks.finance/
  • https://xapp.folks.finance/deposit
  • https://xapp.folks.finance/loans
  • https://xapp.folks.finance/account
  • https://xapp.folks.finance/account
External links
6

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "web.app",
    "issuers": [
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "ogUrl": "https://xapp.folks.finance",
    "title": "Folks Finance",
    "ogType": "website",
    "ogImage": "https://xapp.folks.finance/opengraph-image",
    "ogTitle": "Folks Finance",
    "ogSiteName": "Folks Finance",
    "description": "Lend and borrow crypto with ease across multiple chains. Powered by Chainlink, Wormhole, and Circle messaging layers technology.",
    "twitterCard": "summary_large_image",
    "twitterSite": "@FolksFinance",
    "canonicalUrl": "https://xapp.folks.finance/",
    "ogDescription": "Lend and borrow crypto with ease across multiple chains. Powered by Chainlink, Wormhole, and Circle messaging layers technology.",
    "twitterCreator": "@FolksFinance"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 14,
        "tls": 30,
        "wait": 21,
        "connect": 18,
        "download": 74
    },
    "response_ms": 157
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 367716,
    "co2_grams": 0.0134,
    "cleaner_than": 1
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.38.99",
            "host": "ns4.googledomains.com"
        },
        {
            "ip": "216.239.34.99",
            "host": "ns2.googledomains.com"
        },
        {
            "ip": "216.239.32.99",
            "host": "ns1.googledomains.com"
        },
        {
            "ip": "216.239.36.99",
            "host": "ns3.googledomains.com"
        }
    ],
    "zone": "web.app"
}
Location
{
    "ip": "2620:0:890::100",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "city": "Mountain View",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR4",
    "subject": "web.app"
}
DNS records
{
    "A": [
        "199.36.158.100"
    ],
    "AAAA": [
        "2620:0:890::100"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31556926; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31556926; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2620:0:890::100",
    "family": 6
}
Redirects
{
    "chain": [
        "https://xapp-folks-finance.web.app"
    ]
}
Social profiles
{
    "profiles": [
        "https://x.com/FolksFinance"
    ]
}
Page links
{
    "external": [
        "https://forum.folks.finance/t/xchain-transition-plan-moving-to-the-next-product-evolution/2063",
        "https://xapp.folks.finance/",
        "https://xapp.folks.finance/deposit",
        "https://xapp.folks.finance/loans",
        "https://xapp.folks.finance/account",
        "https://xapp.folks.finance/account"
    ],
    "external_count": 6
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
    }
}
Security Signals
SA Scamadviser Warnings 31/100
The Tranco rank (how much traffic) is rather low An iframe has been detected within the website A (free) development platform is used by this website
We found a valid SSL certificate DNSFilter labels this site as safe

Questions about xapp-folks-finance.web.app

Is xapp-folks-finance.web.app legit?

PhishDestroy records the captured Folks Finance lending page at xapp-folks-finance.web.app, showing wallet connection and market listings.

Is xapp-folks-finance.web.app safe to connect a wallet?

This report does not record which wallet requests xapp-folks-finance.web.app makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used xapp-folks-finance.web.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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 matchesMetaMask · ScamSniffer · PhishDestroy · SEAL · no match in the other 8 4
MetaMask Listed View source
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

All capture links and hashes (3)
xapp-folks-finance.web.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, ScamSniffer, 6/92 VirusTotal engines. PhishDestroy risk score 84/100 (critical).
Social preview card xapp-folks-finance.web.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, ScamSniffer, 6/92 VirusTotal engines. PhishDestroy risk score 84/100 (critical). v d44438f1ef0b

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 100 report ↗
IP Context United States199.36.158.100 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 23, 2026score 20/1009 brand signals
Submitted URLhttp://xapp-folks-finance.web.app/
Favicon Hash
Observed page title
Folks Finance
Automated brand references
Across Arbitrum Avalanche Benqi Chainlink Ethereum Monad Polygon +1
TLS Certificate
Issued by Google Trust Services / WR4 · stored validity ends in 51 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States199.36.158.100
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
Fastly, Inc.
Observed location
United StatesMountain View, US

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR4
Valid from
2026-09-23 17:59:58
Valid until
2026-12-22 17:59:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Certificate names · 2 SANs
  • web.app
  • *.web.app

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-01 02:56:49 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: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-01 02:56:49 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:11:48 UTC last content: 2026-10-31 23:11:48 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.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
VIPRE
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.

Captured network requests

Network requests: 38 SHA-256 hashes: 38 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 02:01 UTC.

Open this scan on URLScan 01a1654c-da4e-763f-a949-8ce5fbcc7e8e ↗

Stored observation history2

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

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations38

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:56:49.000000
    Evidence SHA-256
    5673693ce0e780c2d3c33ca3046405f75f6eccefcfbad3805e193227fe6accc9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:56:49
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:56:49.000000
    Evidence SHA-256
    5673693ce0e780c2d3c33ca3046405f75f6eccefcfbad3805e193227fe6accc9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:56:49
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:11:48.000000
    Evidence SHA-256
    a278698c39fd7ee0f6b5b1bf1c6245138edbf6c7e8cd59a491e12579d328560e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:11:48
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:11:48.000000
    Evidence SHA-256
    a278698c39fd7ee0f6b5b1bf1c6245138edbf6c7e8cd59a491e12579d328560e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:11:48
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:12:34.000000
    Evidence SHA-256
    29debbc6c3290f8b1b2a08e19a8c5dcb38317dde7c6e696afb6d077fa048d4c4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:12:34
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:12:34.000000
    Evidence SHA-256
    29debbc6c3290f8b1b2a08e19a8c5dcb38317dde7c6e696afb6d077fa048d4c4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:12:34
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:33:40.000000
    Evidence SHA-256
    8bffc0fbc622c7ea50a9aaf39a0f652fed2ea9f676b523af658580e702cbf2d7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:33:40
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:33:40.000000
    Evidence SHA-256
    8bffc0fbc622c7ea50a9aaf39a0f652fed2ea9f676b523af658580e702cbf2d7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:33:40
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:20.000000
    Evidence SHA-256
    3717b3aca51a385830705b64173cca9c6b85e1d8c5bfb785c16459c2e46eb01a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:10:20
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:20.000000
    Evidence SHA-256
    3717b3aca51a385830705b64173cca9c6b85e1d8c5bfb785c16459c2e46eb01a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:10:20
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:33.000000
    Evidence SHA-256
    7e41145407aadc1b1b19be9983763884388bc12a2cc777ea064e1400f1ee5b79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:10:33
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:33.000000
    Evidence SHA-256
    7e41145407aadc1b1b19be9983763884388bc12a2cc777ea064e1400f1ee5b79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:10:33
    Evidence reason
    alive_content
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:02.000000
    Evidence SHA-256
    7f18af087f6d10635a91602414f157fd4363ab164f7194eb2c75c941e102a112
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:11:02
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:02.000000
    Evidence SHA-256
    7f18af087f6d10635a91602414f157fd4363ab164f7194eb2c75c941e102a112
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:11:02
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:42.000000
    Evidence SHA-256
    feb0bfe45c72fa647f80544e6b2432b91cbfbf78c3cb17a0af3cc0698ca07ea1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:39:42
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:42.000000
    Evidence SHA-256
    feb0bfe45c72fa647f80544e6b2432b91cbfbf78c3cb17a0af3cc0698ca07ea1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:39:42
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:08.000000
    Evidence SHA-256
    54b31c870952e98a01c46f506cf52cae4a469bcdeef1bb257a82debfe0385e79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:06:08
    Evidence reason
    alive_content
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:08.000000
    Evidence SHA-256
    54b31c870952e98a01c46f506cf52cae4a469bcdeef1bb257a82debfe0385e79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:06:08
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:06:34.000000
    Evidence SHA-256
    c197bacf5665a9bbd054b1e0bd9b98ce78cb65ff413c76d35b317945d1ce422e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:06:34
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:06:34.000000
    Evidence SHA-256
    c197bacf5665a9bbd054b1e0bd9b98ce78cb65ff413c76d35b317945d1ce422e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:06:34
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:26.000000
    Evidence SHA-256
    0e12f49c1d7919e71d1b8f57fcfdd68ce894b1528e3059d1c6c76e0f986315b6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:06:26
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:26.000000
    Evidence SHA-256
    0e12f49c1d7919e71d1b8f57fcfdd68ce894b1528e3059d1c6c76e0f986315b6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:06:26
    Evidence reason
    alive_content
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:18.000000
    Evidence SHA-256
    b2ca5753a9dd121cd6f6ea00f7e31461989dc37d69b629e400a73086d3d4bfdc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:18
    Evidence reason
    alive_content
  24. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:18.000000
    Evidence SHA-256
    b2ca5753a9dd121cd6f6ea00f7e31461989dc37d69b629e400a73086d3d4bfdc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:18
    Evidence reason
    alive_content
  25. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:01:38.000000
    Evidence SHA-256
    0c4ec5d66a1704fb4d9772052a95c47112314a03b2cd485cb58086aec5b7a85d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:38
    Evidence reason
    alive_content
  26. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:01:38.000000
    Evidence SHA-256
    0c4ec5d66a1704fb4d9772052a95c47112314a03b2cd485cb58086aec5b7a85d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:38
    Evidence reason
    alive_content
  27. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:46.000000
    Evidence SHA-256
    e6510068316e51f7829f2daec4ed0bfd072cf6dc89b85d15aa596b739bb369eb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:01:46
    Evidence reason
    alive_content
  28. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:46.000000
    Evidence SHA-256
    e6510068316e51f7829f2daec4ed0bfd072cf6dc89b85d15aa596b739bb369eb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:01:46
    Evidence reason
    alive_content
  29. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:54:34.000000
    Evidence SHA-256
    16fb0f996e1c9af9c2d50477f843264d27cb078a857227269d1fbc51cb0b91de
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:34
    Evidence reason
    alive_content
  30. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:54:34.000000
    Evidence SHA-256
    16fb0f996e1c9af9c2d50477f843264d27cb078a857227269d1fbc51cb0b91de
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:34
    Evidence reason
    alive_content
  31. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:00:39.000000
    Evidence SHA-256
    5b8c9b2c5b3e9ad8c72625573ee3e5d7fe88cca3683f15738deb2416102f7684
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:39
    Evidence reason
    alive_content
  32. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:00:39.000000
    Evidence SHA-256
    5b8c9b2c5b3e9ad8c72625573ee3e5d7fe88cca3683f15738deb2416102f7684
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:39
    Evidence reason
    alive_content
  33. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:00:49.000000
    Evidence SHA-256
    0278ee0d53bbc333dea843224a860016518dcb3c7e991671ccd9a768914d2795
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:49
    Evidence reason
    alive_content
  34. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:00:49.000000
    Evidence SHA-256
    0278ee0d53bbc333dea843224a860016518dcb3c7e991671ccd9a768914d2795
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:49
    Evidence reason
    alive_content
  35. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:00:41.000000
    Evidence SHA-256
    59881c1f82d2dc1f9c57581804d24a3575f70cd6682461662c658465eb3f57b5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:41
    Evidence reason
    alive_content
  36. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:00:41.000000
    Evidence SHA-256
    59881c1f82d2dc1f9c57581804d24a3575f70cd6682461662c658465eb3f57b5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:41
    Evidence reason
    alive_content
  37. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 22:29:12.000000
    Evidence SHA-256
    2516a1094f518decfe981ba22cdbea1939d21e38cd8a003f33e0ce4652f6c5ca
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:29:12
    Evidence reason
  38. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 22:29:12.000000
    Evidence SHA-256
    2516a1094f518decfe981ba22cdbea1939d21e38cd8a003f33e0ce4652f6c5ca
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:29:12
    Evidence reason

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: 1 of 1
  • Threat Ingested
    xapp-folks-finance.web.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · VirusTotal · Blocklist Detection · Automated brand label: Arbitrum · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 100
  • VirusTotal
    Detections recorded on VirusTotal: 3/92
  • Blocklist Detection
    Found in blocklists: MetaMask, ScamSniffer, SEAL
  • Automated brand label: Arbitrum
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. Added to PhishDestroy

    xapp-folks-finance.web.app

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    3/92 engine detections

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

Lookalike domains

28 stored lookalike domains

a.rbitrum.io subdomain A 188.114.96.3 abitrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com abritrum.io transposition A 188.114.96.3NS hank.ns.cloudflare.com arbbitrum.io repetition A 185.53.179.128NS ns1.dyna-ns.net arbiitrum.io repetition A 185.53.179.128NS ns1.dyna-ns.net arbirtum.io transposition A 188.114.96.3NS hank.ns.cloudflare.com arbirum.io omission A 199.91.220.73NS ns1.dnsowl.com arbit.rum.io subdomain A 13.248.169.48NS ns1.afternic.com arbitr.um.io subdomain A 3.139.159.151 arbitram.io vowel-swap A 77.247.179.86NS ns1.badgerdns.com arbitrium.io insertion A 88.212.204.58MX mx.yandex.netNS c.ns.over.ru arbitrm.io omission A 104.21.28.233NS hank.ns.cloudflare.com
Show all (16)
arbitrmu.io transposition A 185.53.179.128NS ns1.dyna-ns.net arbitru.io omission A 104.21.2.146NS hank.ns.cloudflare.com arbitruum.io repetition A 185.53.179.128NS ns1.dyna-ns.net arbittrum.io insertion A 185.53.179.128NS ns1.dyna-ns.net arbitum.io omission A 104.21.95.219NS hank.ns.cloudflare.com arbiturm.io transposition A 185.53.179.128NS ns1.dyna-ns.net arbtirum.io transposition A 185.53.179.128NS ns1.dyna-ns.net arbtrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com aribtrum.io transposition A 199.91.220.73NS ns1.dnsowl.com aritrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com rabitrum.io transposition A 185.53.179.128NS ns1.dyna-ns.net rbitrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com arbitrrum.io insertion A 104.21.56.168NS hank.ns.cloudflare.com arbitrumm.io addition A 185.53.179.128NS ns1.dyna-ns.net arbitrun.io homoglyph A 104.21.88.223NS hank.ns.cloudflare.com xn--rbitrum-r3a.io homoglyph A 104.21.60.23NS dalary.ns.cloudflare.com

Check for cloaking

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

xapp-folks-finance.web.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If 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.

Official reporting routes

More official reporting routes
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.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
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

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 xapp-folks-finance.web.app)
  • 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/xapp-folks-finance.web.app"
  title="PhishDestroy threat report for xapp-folks-finance.web.app"
  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>