Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 16/92 engines flagged. malicious: 16. suspicious: 0. Analysis time (as stored): 2026-11-03T23:59:13Z. Retrieved (as stored): 2026-11-08T01:42:00Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
pagecommunity-centerpolicy.pages.dev favicon

pagecommunity-centerpolicy.pages.dev

In short

PhishDestroy first recorded pagecommunity-centerpolicy.pages.dev on 2026-11-07. Stored VirusTotal result: 16/92 engines flagged. malicious: 16. suspicious: 0. Analysis time (as stored): 2026-11-03T23:59:13Z. Retrieved (as stored): 2026-11-08T01:42:00Z.

“Privacy Policy”

Review the evidence
Registrar
United StatesCloudFlare
Resolved IP
United Kingdom188.114.96.1CloudFLARENET-EU · CDN
First observed
Nov 7, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 16/92
VirusTotal
16 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 90
Page captures
2
open gallery
Nov 7, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded pagecommunity-centerpolicy.pages.dev on 2026-11-07. Stored VirusTotal result: 16/92 engines flagged. malicious: 16. suspicious: 0. Analysis time (as stored): 2026-11-03T23:59:13Z. Retrieved (as stored): 2026-11-08T01:42:00Z. Risk: critical (100/100). Registrar: CloudFlare. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
16 / 92
Hosting
United Kingdom188.114.96.1CloudFLARENET-EU · CDN
Registrar
United StatesCloudFlare
Page captures
2
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for pagecommunity-centerpolicy.pages.dev. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 16 / 92 6 sources

VirusTotal

16 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
16
Suspicious
0
Undetected
31

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
BitDefender
phishing
Criminal IP
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

CloudFlare, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    dell.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.66.45.9
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2ef7
  • TTL, seconds
    300
    Type
    A
    Value
    172.66.46.247
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2d09
  • TTL, seconds
    21600
    Type
    NS
    Value
    kareem.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    dell.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • pagecommunity-centerpolicy.pages.dev
  • *.pagecommunity-centerpolicy.pages.dev
Issuer
Google Trust Services / WE1
Serial
561d4e015462b26313dc13625c452a27
SHA-256
781aa458d790fc45935a7cb8bb417b2a1365f0b6cdf3005a2b5aa64f2e9b3514
Subject
pagecommunity-centerpolicy.pages.dev
Valid until
Valid from

Registration record

Registrar
CloudFlare, Inc.
Registrar IANA ID
1910
Registrar URL
None
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
  • clientdeleteprohibited
  • clienttransferprohibited
  • clientupdateprohibited
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 16,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
CloudFlare, Inc.
Created
2020-09-02T02:33:29Z
Expires
2026-09-02T02:33:29Z
Updated
2025-03-17T14:56:22Z
First seen
2024-08-25T18:54:17Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "dell.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.45.9"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2ef7"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.46.247"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2d09"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kareem.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "dell.ns.cloudflare.com"
    }
]
Dns at
2026-11-03T23:59:27Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "pagecommunity-centerpolicy.pages.dev",
        "*.pagecommunity-centerpolicy.pages.dev"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "561d4e015462b26313dc13625c452a27",
    "sha256": "781aa458d790fc45935a7cb8bb417b2a1365f0b6cdf3005a2b5aa64f2e9b3514",
    "subject": "pagecommunity-centerpolicy.pages.dev",
    "valid_to": "2026-12-31T03:26:52Z",
    "valid_from": "2026-10-02T02:26:58Z"
}
Registration record
{
    "registrar": "CloudFlare, Inc.",
    "registrar_iana_id": "1910",
    "registrar_url": "None",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2023-09-04T18:15:07Z",
    "expires": "2026-09-02T02:33:29Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "clientdeleteprohibited",
        "clienttransferprohibited",
        "clientupdateprohibited"
    ],
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
16
denominator
92
malicious
null
suspicious
null
vendors
["Criminal IP","alphaMountain.ai","BitDefender","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","G-Data","Gridinsoft","Kaspersky","LevelBlue","Lionic","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-11-03 23:59:13
checked_at
2026-11-08 02:42:01
fetched_at
2026-11-08 01:42:01
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 90

SHA-256 02b735769b003b9c46ff3d1879d260a7102f33939682bfec5dd19ac52c3fe493

Open report
URLScanOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Report ID

019f9aea-150e-7776-9d20-03321278c310

Final URL

https://pagecommunity-centerpolicy.pages.dev/

HTTP response

200

IP address

2a06:98c1:3120::3

Contacted domains

  • cdn.jsdelivr.net

Contacted IP addresses

  • 2606:4700::6811:d005
  • 2a06:98c1:3120::3

Autonomous systems (ASN)

  • 13335

Document hash

4d55145845782f0012a4a2fd205d40dc3a8785dd538e49ca8809a2a7c206d537

TLS session and certificate

Subject alternative names
  • pagecommunity-centerpolicy.pages.dev
  • *.pagecommunity-centerpolicy.pages.dev
Cipher
AES_128_GCM
Issuer
WE1
Subject
pagecommunity-centerpolicy.pages.dev
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

699

Registered domain age, days

699

Certificate age, days

49

Certificate validity, days

90

Page requests

9

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Uuid
019f9aea-150e-7776-9d20-03321278c310
Final url
https://pagecommunity-centerpolicy.pages.dev/
Status
200
Ip
2a06:98c1:3120::3
Contacted domains
[
    "cdn.jsdelivr.net"
]
Contacted IP addresses
[
    "2606:4700::6811:d005",
    "2a06:98c1:3120::3"
]
Asns
[
    "13335"
]
Document hash
4d55145845782f0012a4a2fd205d40dc3a8785dd538e49ca8809a2a7c206d537
Tls
{
    "san": [
        "pagecommunity-centerpolicy.pages.dev",
        "*.pagecommunity-centerpolicy.pages.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "pagecommunity-centerpolicy.pages.dev",
    "protocol": "TLS 1.3",
    "valid_to": "2026-09-04T00:55:24Z",
    "valid_from": "2026-06-05T23:55:41Z"
}
Domain age days
699
Apex age days
699
Tls age days
49
Tls valid days
90
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 90,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Separate monitor record · 2026-11-08 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
019f9aea-150e-7776-9d20-03321278c310
score
0
malicious
false
result_at
2026-11-08T04:30:14Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-11-08 05:30:14","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

afb14906-6791-490e-a074-9ced280fe557

Final URL

https://pagecommunity-centerpolicy.pages.dev/

HTTP response

200

Navigation history

  • URL
    https://pagecommunity-centerpolicy.pages.dev/
    Status
    200

DOM structure hash

a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e

Document hash

4d55145845782f0012a4a2fd205d40dc3a8785dd538e49ca8809a2a7c206d537

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    pagecommunity-centerpolicy.pages.dev
    Type
    A
    Value
    188.114.97.0
  • Name
    pagecommunity-centerpolicy.pages.dev
    Type
    A
    Value
    188.114.96.0
  • Name
    pagecommunity-centerpolicy.pages.dev
    Type
    AAAA
    Value
    2a06:98c1:3120::
  • Name
    pagecommunity-centerpolicy.pages.dev
    Type
    AAAA
    Value
    2a06:98c1:3121::

DNSSEC valid

No

IP address

127.0.1.10

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

Registration record

Registrar
CloudFlare, Inc.
Registered
Updated
Expires
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
Original source fields · JSON
Uuid
afb14906-6791-490e-a074-9ced280fe557
Final url
https://pagecommunity-centerpolicy.pages.dev/
Status
200
History
[
    {
        "url": "https://pagecommunity-centerpolicy.pages.dev/",
        "status": 200
    }
]
DOM structure hash
a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e
Document hash
4d55145845782f0012a4a2fd205d40dc3a8785dd538e49ca8809a2a7c206d537
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "pagecommunity-centerpolicy.pages.dev",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "pagecommunity-centerpolicy.pages.dev",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "pagecommunity-centerpolicy.pages.dev",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "pagecommunity-centerpolicy.pages.dev",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
127.0.1.10

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

Registration record
{
    "registrar": "CloudFlare, Inc.",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2026-06-09T12:00:52Z",
    "expires": "2027-09-02T02:33:29Z",
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

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

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Page title and metadata

Open Graph URL
/meta-community-standard
Page title
Privacy Policy
Open Graph type
website
Open Graph image
/static/uploads/1c325477ab8db1be14392399bff625fc.png
Open Graph title
Privacy Policy

Trackers

Requests
8
Observed services
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://cdn.jsdelivr.net/npm/disable-devtool@latest
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
15
Waiting
47
Connection
9
Download
0
Response time, ms
73

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
1455
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    108.162.192.94
    Host
    dell.ns.cloudflare.com
  • IP address
    172.64.35.22
    Host
    kareem.ns.cloudflare.com
DNS zone
pagecommunity-centerpolicy.pages.dev

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
pagecommunity-centerpolicy.pages.dev

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • dell.ns.cloudflare.com
  • kareem.ns.cloudflare.com
SOA
Primary nameserver
dell.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416397332
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

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
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3121::3
IP version
6

Redirects

Redirect chain
  • https://pagecommunity-centerpolicy.pages.dev

Technology stack

Technologies
  • HSTS
  • Cloudflare
  • HTTP/3

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2024-12-27T10:02:40Z",
    "first": "2024-08-25T21:57:26Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.01,
    "avg_page_bytes": 1074
}
Page title and metadata
{
    "ogUrl": "/meta-community-standard",
    "title": "Privacy Policy",
    "ogType": "website",
    "ogImage": "/static/uploads/1c325477ab8db1be14392399bff625fc.png",
    "ogTitle": "Privacy Policy"
}
Trackers
{
    "requests": 8,
    "trackers": [
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.jsdelivr.net/npm/disable-devtool@latest"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 15,
        "wait": 47,
        "connect": 9,
        "download": 0
    },
    "response_ms": 73
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 1455,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.192.94",
            "host": "dell.ns.cloudflare.com"
        },
        {
            "ip": "172.64.35.22",
            "host": "kareem.ns.cloudflare.com"
        }
    ],
    "zone": "pagecommunity-centerpolicy.pages.dev"
}
Location
{
    "ip": "2a06:98c1:3121::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "pagecommunity-centerpolicy.pages.dev"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "NS": [
        "dell.ns.cloudflare.com",
        "kareem.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"dell.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416397332, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3121::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://pagecommunity-centerpolicy.pages.dev"
    ]
}
Tech stack
{
    "technologies": [
        "HSTS",
        "Cloudflare",
        "HTTP/3"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}

Questions about pagecommunity-centerpolicy.pages.dev

Is pagecommunity-centerpolicy.pages.dev legit?

PhishDestroy rates pagecommunity-centerpolicy.pages.dev as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 16/92 engines flagged. malicious: 16. suspicious: 0. Analysis time (as stored): 2026-11-03T23:59:13Z. Retrieved (as stored): 2026-11-08T01:42:00Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is pagecommunity-centerpolicy.pages.dev safe to connect a wallet?

This report does not record which wallet requests pagecommunity-centerpolicy.pages.dev 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 pagecommunity-centerpolicy.pages.dev?

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 · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

URLScan · 2026-03-20 1 / 2
SourceURLScan · 2026-03-20
Recorded
StateStored capture
HTTP status200
Final URLhttps://pagecommunity-centerpolicy.pages.dev/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 90 report ↗
IP Context United Kingdom188.114.96.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider CloudFlare US(US)
Abuse contact["registrar-abuse@cloudflare.com", "256f9e523b2ede94s@"]
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
Submitted URLhttp://pagecommunity-centerpolicy.pages.dev/
Favicon Hash
Observed page title
Privacy Policy
TLS Certificate
Issued by WE1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.1
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com

SOA

  • nsname: dell.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2416397332
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-06-05 23:55:41
Valid until
2026-09-04 00:55:24
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint781aa458d790fc45935a7cb8bb417b2a1365f0b6cdf3005a2b5aa64f2e9b3514
Certificate names · 2 SANs
  • pagecommunity-centerpolicy.pages.dev
  • *.pagecommunity-centerpolicy.pages.dev

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

viewdns.info · 188.114.96.1rapiddns.io

Latest Classified Outcome 2026-11-07 23:00:48 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: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-07 23:00:48 UTC
RDAP registration
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
SOCRadar
Kaspersky
LevelBlue
Gridinsoft
BitDefender
Criminal IP
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Captured network requests

Network requests: 9 SHA-256 hashes: 8 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-07 14:28 UTC.

Open this scan on URLScan 019f9aea-150e-7776-9d20-03321278c310 ↗

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

    live_content

    content_served

All retained availability observations3

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-08 00:00:48.000000
    Evidence SHA-256
    45309fe1813cc6195a90ba8f057804006bb3cccf3e85366763a116f703794756
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:00:48
    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-08 00:00:48.000000
    Evidence SHA-256
    45309fe1813cc6195a90ba8f057804006bb3cccf3e85366763a116f703794756
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:00:48
    Evidence reason
    alive_content
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 15:31:43.312418
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

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
    pagecommunity-centerpolicy.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · 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: 90
  • 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
  • VirusTotal
    Detections recorded on VirusTotal: 16/92
  • 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

    pagecommunity-centerpolicy.pages.dev

    View source
  3. VirusTotal

    16/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 90

    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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

pagecommunity-centerpolicy.pages.dev

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery SSL Labs Stored certificate expired or unverified 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?

3 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 pagecommunity-centerpolicy.pages.dev)
  • 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.

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/pagecommunity-centerpolicy.pages.dev"
  title="PhishDestroy threat report for pagecommunity-centerpolicy.pages.dev"
  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>