Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
meta.pagey.site favicon

meta.pagey.site

In short

PhishDestroy records the Word Collector page on meta.pagey.site, where visitors are prompted to enter words and log in to install.

“Word Collector”

Review the evidence
Registrar
United StatesNamecheap
Resolved IP
Germany92.118.190.50xTom GmbH
Registered
Oct 9, 2025
First observed
Nov 1, 2026
PhishDestroy assessment High
58/100
Evidence score
Availability Last known active Latest stored reachability observation Observed Website checks · HTTP 200
Risk signals
Stored blocklist matches: 1
VirusTotal
0 / 92
engine detections ·
Blocklist matches
1
SEAL
URLScan
Malicious
engine verdict · score 48
Page captures
6
open gallery
Domain age
387 days
registered 2025-10-09 according to WHOIS · source data differ
Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the Word Collector page on meta.pagey.site, where visitors are prompted to enter words and log in to install.

High
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
1
Hosting
Germany92.118.190.50xTom GmbH
Registrar
United StatesNamecheap
Registered
Oct 9, 2025
Page captures
6
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page on meta.pagey.site presents a single card headed "Share Your Words Securely" with a text area labeled "Enter your words here..." and an orange "Login and Install" button beneath it. The page title is "Word Collector," and a small badge in the lower-right corner reads "Site Hosted on pagey.site." The main interaction is entering text into the field and pressing the button, which the page frames as a secure way to share words.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidenceVirusTotal 0 / 92 7 sources

URLScan

Malicious · engine verdict · score 48

SHA-256 813b44b98b0751a1d08f60d8a119175f46183c03771252205a3dde13fb958958

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a19457-f812-72d3-9040-c44c51ab9fbc

Final URL

https://meta.pagey.site/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://meta.pagey.site/
    From
    http://meta.pagey.site/
    Status
    307

IP address

92.118.190.50

Contacted domains

  • a.jerrysniffs.online
  • fonts.gstatic.com
  • pagey.site
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.110.94
  • 2a00:1450:4001:c15::5f
  • 92.118.190.50

Autonomous systems (ASN)

  • 15169
  • 3214

Server countries

  • US
  • DE

Linked domains

  • pagey.site

Document hash

813b44b98b0751a1d08f60d8a119175f46183c03771252205a3dde13fb958958

Script hashes

  • 0c03397a6b10b57152889f1e190d10aed3ca56c664ad53b1722238e536cb5166

JavaScript globals

  • umami
  • form
  • message

TLS session and certificate

Subject alternative names
  • *.pagey.site
  • pagey.site
Cipher
AES_128_GCM
Issuer
YE1
Subject
*.pagey.site
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Differs from the registration date in WHOIS (2025-10-09), which gives 387 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1284

Differs from the registration date in WHOIS (2025-10-09), which gives 387 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

37

Certificate validity, days

89

Page requests

8

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
X-powered-by
Express
Original source fields · JSON
Uuid
01a19457-f812-72d3-9040-c44c51ab9fbc
Final url
https://meta.pagey.site/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://meta.pagey.site/",
        "from": "http://meta.pagey.site/",
        "status": 307
    }
]
Ip
92.118.190.50
Contacted domains
[
    "a.jerrysniffs.online",
    "fonts.gstatic.com",
    "pagey.site",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.110.94",
    "2a00:1450:4001:c15::5f",
    "92.118.190.50"
]
Asns
[
    "15169",
    "3214"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "pagey.site"
]
Document hash
813b44b98b0751a1d08f60d8a119175f46183c03771252205a3dde13fb958958
Script hashes
[
    "0c03397a6b10b57152889f1e190d10aed3ca56c664ad53b1722238e536cb5166"
]
Globals
[
    "umami",
    "form",
    "message"
]
Tls
{
    "san": [
        "*.pagey.site",
        "pagey.site"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "*.pagey.site",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-23T06:04:22Z",
    "valid_from": "2026-09-24T06:04:23Z"
}
Domain age days
1

Differs from the registration date in WHOIS (2025-10-09), which gives 387 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
1284

Differs from the registration date in WHOIS (2025-10-09), which gives 387 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
37
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 48,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "Express"
}

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
0
Suspicious
0
Undetected
92

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    1799
    Type
    A
    Value
    92.118.190.50

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.pagey.site
  • pagey.site
Issuer
Let's Encrypt / YE1
Serial
6cf77c5c7c942bb1bb43ce1e4de1d71aadf
SHA-256
a11a9a3744bb72f590574eb40fda7e1f50b80aab3a07e53e94b207bf69df0009
Subject
*.pagey.site
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
NAMECHEAP INC
Registrar IANA ID
1068
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
Reputation
0
Created
2025-10-09T00:00:00Z
Updated
2025-10-09T00:00:00Z
First seen
2026-10-31T09:49:19Z
DNS records
[
    {
        "ttl": 1799,
        "type": "A",
        "value": "92.118.190.50"
    }
]
Dns at
2026-10-31T09:49:29Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.pagey.site",
        "pagey.site"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6cf77c5c7c942bb1bb43ce1e4de1d71aadf",
    "sha256": "a11a9a3744bb72f590574eb40fda7e1f50b80aab3a07e53e94b207bf69df0009",
    "subject": "*.pagey.site",
    "valid_to": "2026-12-23T06:04:22Z",
    "valid_from": "2026-09-24T06:04:23Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-09-24T06:58:30Z",
        "registration": "2025-10-09T12:52:24Z",
        "registrar expiration": "2027-10-09T23:59:59Z",
        "last update of RDAP database": "2026-10-31T09:49:28Z"
    },
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-31 09:49:06 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-31T09:49:06Z
fetched_at
2026-11-01T00:16:05Z
stats
{"timeout":0,"harmless":0,"malicious":0,"suspicious":0,"undetected":92}

OTX

no community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

59616dbc-f58e-4ecb-8812-a66bbe89552f

Final URL

https://meta.pagey.site/

HTTP response

200

Navigation history

  • URL
    https://meta.pagey.site/
    Status
    200

DOM structure hash

add03744b9534804780746202ea74ffe1c50717b16f2ecddf6b6cbc7aba81d03

Document hash

813b44b98b0751a1d08f60d8a119175f46183c03771252205a3dde13fb958958

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    meta.pagey.site
    Type
    A
    Value
    92.118.190.50
  • Name
    pagey.site
    Type
    A
    Value
    92.118.190.50

DNSSEC valid

No

IP address

127.0.1.5

127.0.1.5 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
NameCheap, Inc.
Registered
Updated
Expires
Nameservers
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
Original source fields · JSON
Uuid
59616dbc-f58e-4ecb-8812-a66bbe89552f
Final url
https://meta.pagey.site/
Status
200
History
[
    {
        "url": "https://meta.pagey.site/",
        "status": 200
    }
]
DOM structure hash
add03744b9534804780746202ea74ffe1c50717b16f2ecddf6b6cbc7aba81d03
Document hash
813b44b98b0751a1d08f60d8a119175f46183c03771252205a3dde13fb958958
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "meta.pagey.site",
        "type": "A",
        "value": "92.118.190.50"
    },
    {
        "name": "pagey.site",
        "type": "A",
        "value": "92.118.190.50"
    }
]
Dnssec valid
false
Ip
127.0.1.5

127.0.1.5 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2025-10-09T12:52:24Z",
    "updated": "2026-09-29T06:59:04Z",
    "expires": "2027-10-09T23:59:59Z",
    "nameservers": [
        "dns1.registrar-servers.com",
        "dns2.registrar-servers.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

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
meta.pagey.site Word Collector word-sharing page
ai_description
PhishDestroy records the Word Collector page on meta.pagey.site, where visitors are prompted to enter words and log in to install.
ai_summary
The captured page on meta.pagey.site presents a single card headed "Share Your Words Securely" with a text area labeled "Enter your words here..." and an orange "Login and Install" button beneath it. The page title is "Word Collector," and a small badge in the lower-right corner reads "Site Hosted on pagey.site." The main interaction is entering text into the field and pressing the button, which the page frames as a secure way to share words. The stored VirusTotal domain result reports 0 detections out of 92 engines.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 01:17:05
revision
7774640ef29b26afd2cfc88cb19779d2bc697f6ee58799067850d95f3e9212b7
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: 23 fields

CAA records

Domain
meta.pagey.site

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
2223

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://pagey.site/sitemap.xml

Sitemap

Present
Yes
URL count
13

Page title and metadata

Page title
Word Collector

Trackers

Requests
6
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://a.jerrysniffs.online/script.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
24
TLS
21
Waiting
14
Connection
7
Download
0
Response time, ms
66

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
  • 22
  • 80
  • 443

Carbon estimate

Bytes
4562
CO₂, grams
0.0002
Cleaner than, %
89

DNS servers

Nameservers
  • IP address
    156.154.133.200
    Host
    dns2.registrar-servers.com
  • IP address
    156.154.132.200
    Host
    dns1.registrar-servers.com
DNS zone
pagey.site

Location

IP address
92.118.190.50
ASN
3214
Organization
xTom GmbH
City
Frankfurt Am Main
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
*.pagey.site

DNS records

A
  • 92.118.190.50

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
92.118.190.50
IP version
4

Redirects

Redirect chain
  • https://meta.pagey.site

Registration record

Registrar
NameCheap, Inc.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
X-powered-by
Express
Original source fields · JSON
Caa records
{
    "domain": "meta.pagey.site"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T23:44:13Z",
    "first": "2026-10-31T23:44:13Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2223
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://pagey.site/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 13
}
Page title and metadata
{
    "title": "Word Collector"
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://a.jerrysniffs.online/script.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 24,
        "tls": 21,
        "wait": 14,
        "connect": 7,
        "download": 0
    },
    "response_ms": 66
}
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": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 4562,
    "co2_grams": 0.0002,
    "cleaner_than": 89
}
Dns server
{
    "ns": [
        {
            "ip": "156.154.133.200",
            "host": "dns2.registrar-servers.com"
        },
        {
            "ip": "156.154.132.200",
            "host": "dns1.registrar-servers.com"
        }
    ],
    "zone": "pagey.site"
}
Location
{
    "ip": "92.118.190.50",
    "asn": "3214",
    "org": "xTom GmbH",
    "city": "Frankfurt Am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "*.pagey.site"
}
DNS records
{
    "A": [
        "92.118.190.50"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "92.118.190.50",
    "family": 4
}
Redirects
{
    "chain": [
        "https://meta.pagey.site"
    ]
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2025-10-09T12:52:24Z",
    "updated": "2026-09-29T06:59:04Z",
    "expires": "2027-10-09T23:59:59Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "dns1.registrar-servers.com",
        "dns2.registrar-servers.com"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-powered-by": "Express"
    }
}

Questions about meta.pagey.site

Is meta.pagey.site legit?

PhishDestroy records the Word Collector page on meta.pagey.site, where visitors are prompted to enter words and log in to install.

Is meta.pagey.site safe to connect a wallet?

This report does not record which wallet requests meta.pagey.site 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 meta.pagey.site?

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 matchesPhishDestroy · SEAL · no match in the other 10 2
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 6 captures

Cloudflare Radar 1 / 6 Used in the analysis Source file SHA-256: f93cee1788013ed006b60c25961fbe345168366c4f404b5eaf9e668cf7c5415f SHA-256 of the prepared copy given to the model: 3bba0686d0c23da1ba4eaf905d17a904e34ffe94c98d660c4d6edf1b489efa4f
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://meta.pagey.site/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
Word Collector
TLS Certificate
Issued by YE1 · stored validity ends in 52 days

Domain details

Domain
IP Reputation Germany92.118.190.50 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar (base domain) Namecheap US(US)
Abuse contactabuse@namecheap.com, abuse@greenserver.io
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for pagey.site →
Registration (base domain)pagey.site · Created Oct 9, 2025 — Expires Oct 9, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://meta.pagey.site/
Favicon Hash
ICANN OVERSIGHT Registration: pagey.site

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain pagey.site behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany92.118.190.50
Network ASN
AS3214
Organization
xTom GmbH
Observed location
GermanyFrankfurt Am Main, DE

Nameservers 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-09-24 06:04:23
Valid until
2026-12-23 06:04:22
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta11a9a3744bb72f590574eb40fda7e1f50b80aab3a07e53e94b207bf69df0009
Certificate names · 2 SANs
  • *.pagey.site
  • pagey.site

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

viewdns.info · 92.118.190.50rapiddns.io
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of meta.pagey.site · checked Nov 1, 2026

100
Good
Performance
FCP
1.51 s
First Contentful Paint
LCP
1.51 s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.51 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://meta.pagey.site/
Final URL: https://meta.pagey.site/
Word Collector
Response
HTTP 200
HTML body
4.5 KB
Compressed
1.7 KB
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 5
Content-Length
4562
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 23:44:29 GMT
Etag
W/"11d2-GUgVinzVTbG8GQC7b+antw+bA40"
X-Powered-By
Express

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

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: 8 SHA-256 hashes: 7 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-31 23:44 UTC.

Open this scan on URLScan 01a19457-f812-72d3-9040-c44c51ab9fbc ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-01 00:28:10
All retained availability observations2

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_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-11-01 00:43:26.000000
    Evidence SHA-256
    441c01fed72d12d1d011c55987a06024e49aa92a1304612a25e3375951204c91
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 00:43:26
    Evidence reason
  2. 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-11-01 00:43:26.000000
    Evidence SHA-256
    441c01fed72d12d1d011c55987a06024e49aa92a1304612a25e3375951204c91
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 00:43:26
    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
    meta.pagey.site detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Blocklist Detection · 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: 48
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Blocklist Detection
    Found in blocklists: SEAL
  • 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

4 entries
  1. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    meta.pagey.site

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

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

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

meta.pagey.site

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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 meta.pagey.site)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/meta.pagey.site"
  title="PhishDestroy threat report for meta.pagey.site"
  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>