Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 5/92 engines flagged. malicious: 5. suspicious: 0. Analysis time (as stored): 2026-10-19T10:10:48Z. Retrieved (as stored): 2026-11-02T03:53:32Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev favicon

positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev

In short

The captured page on positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev carries the title UOMP TOPUP and presents a mostly empty light-colored canvas. The only visible element is a circular purple support widget in the lower-right corner, showing a headset icon that suggests a customer-support entry point. No other content, forms or text appear in the capture, so the page's intended top-up interaction is not visible here.

“UOMP TOPUP”

Review the evidence
Registrar
Tencent Cloud
Resolved IP
Singapore43.174.246.29ACE
Registered
Jun 9, 2025
First observed
Nov 2, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 5/92
VirusTotal
5 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 83
Page captures
3
open gallery
Domain age
510 days
registered 2025-06-09 according to RDAP · source data differ
Nov 2, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev on 2026-11-02. Stored VirusTotal result: 5/92 engines flagged. malicious: 5. suspicious: 0. Analysis time (as stored): 2026-10-19T10:10:48Z. Retrieved (as stored): 2026-11-02T03:53:32Z. Risk: critical (80/100). Registrar: Tencent Cloud. Status: Last known active. Hosting: ACE. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
5 / 92
Hosting
Singapore43.174.246.29ACE
Registrar
Tencent Cloud
Registered
Jun 9, 2025
Page captures
3
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-02T03:52:52Z
SHA-256: 92225c6ce519eed961e3079d1f49f121380b7891159000f1aec9e517acd3a9c2

PhishDestroy analysis, reviewed version

The captured page on positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev carries the title UOMP TOPUP and presents a mostly empty light-colored canvas. The only visible element is a circular purple support widget in the lower-right corner, showing a headset icon that suggests a customer-support entry point. No other content, forms or text appear in the capture, so the page's intended top-up interaction is not visible here.

The stored VirusTotal domain result reports 5 detections out of 92 engines. VIPRE reported "phishing"; Webroot reported "malicious".

Source evidenceVirusTotal 5 / 92 7 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
52
Malicious
5
Suspicious
0
Undetected
35

Vendor labels

VIPRE
phishing
Webroot
malicious
SOCRadar
phishing
Gridinsoft
phishing
Yandex Safebrowsing
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    600
    Type
    A
    Value
    43.174.246.29
  • TTL, seconds
    600
    Type
    CNAME
    Value
    2354db541df20c20.edgeone.dev.pages.dnsoe6.com
  • TTL, seconds
    600
    Type
    A
    Value
    43.174.247.29

DNS records observed

JARM fingerprint

2ad2ad0002ad2ad22c42d42d0000008a5941c13f67e0c0a2c8a36bfeef6920

Certificate

Subject alternative names
  • *.edgeone.dev
  • edgeone.dev
Issuer
Let's Encrypt / YR1
Serial
5fb70cbb59204334541800ff2e61c87889d
SHA-256
6d538285ba8e76e272733030941a0f13d96a5ad70d8ff34789947928afe7b1fa
Subject
edgeone.dev
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 5,
    "suspicious": 0,
    "undetected": 35
}
Vendor labels
{
    "VIPRE": "phishing",
    "Webroot": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "Yandex Safebrowsing": "phishing"
}
Reputation
0
Created
2025-06-09T00:00:00Z
Updated
2025-06-09T00:00:00Z
First seen
2026-10-19T10:16:05Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "43.174.246.29"
    },
    {
        "ttl": 600,
        "type": "CNAME",
        "value": "2354db541df20c20.edgeone.dev.pages.dnsoe6.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "43.174.247.29"
    }
]
Dns at
2026-10-19T10:16:09Z
Jarm
2ad2ad0002ad2ad22c42d42d0000008a5941c13f67e0c0a2c8a36bfeef6920
Certificate
{
    "san": [
        "*.edgeone.dev",
        "edgeone.dev"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5fb70cbb59204334541800ff2e61c87889d",
    "sha256": "6d538285ba8e76e272733030941a0f13d96a5ad70d8ff34789947928afe7b1fa",
    "subject": "edgeone.dev",
    "valid_to": "2026-12-16T02:52:53Z",
    "valid_from": "2026-09-17T02:52:54Z"
}
Separate source record · 5 malicious + 0 suspicious / 92 · 2026-10-19 10:10:48 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-19T10:10:48Z
fetched_at
2026-11-02T03:53:32Z
stats
{"timeout":0,"harmless":52,"malicious":5,"suspicious":0,"undetected":35}

URLScan

Malicious · engine verdict · score 83

SHA-256 a17effb7297949d9384e98e7c4a4b9d899fde87867f594706116a3da5602fe48

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a19a62-cb4f-7003-bff3-8fd124c8ad87

Final URL

https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
    From
    http://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
    Status
    307

IP address

43.174.247.29

Contacted domains

  • images.unsplash.com
  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 173.194.45.94
  • 151.101.66.208
  • 173.194.45.95
  • 43.174.247.29

Autonomous systems (ASN)

  • 15169
  • 54113
  • 139341

Server countries

  • US
  • SG

Linked domains

  • t.me

Social media links

  • https://t.me/uomptopup

TLS session and certificate

Subject alternative names
  • *.edgeone.dev
  • edgeone.dev
Cipher
AES_256_GCM
Issuer
YR1
Subject
edgeone.dev
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

13

Differs from the registration date in RDAP (2025-06-09), which gives 510 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1446

Differs from the registration date in RDAP (2025-06-09), which gives 510 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Certificate age, days

46

Certificate validity, days

89

Page requests

7

Provider verdicts

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

HTTP headers

Server
edgeone makers
Content-type
text/html
Original source fields · JSON
Uuid
01a19a62-cb4f-7003-bff3-8fd124c8ad87
Final url
https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/",
        "from": "http://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/",
        "status": 307
    }
]
Ip
43.174.247.29
Contacted domains
[
    "images.unsplash.com",
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "173.194.45.94",
    "151.101.66.208",
    "173.194.45.95",
    "43.174.247.29"
]
Asns
[
    "15169",
    "54113",
    "139341"
]
Countries
[
    "US",
    "SG"
]
Linked domains
[
    "t.me"
]
Social
[
    "https://t.me/uomptopup"
]
Tls
{
    "san": [
        "*.edgeone.dev",
        "edgeone.dev"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "edgeone.dev",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-16T02:52:53Z",
    "valid_from": "2026-09-17T02:52:54Z"
}
Domain age days
13

Differs from the registration date in RDAP (2025-06-09), which gives 510 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Apex age days
1446

Differs from the registration date in RDAP (2025-06-09), which gives 510 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Tls age days
46
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 83,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "edgeone makers",
    "content-type": "text/html"
}
Separate monitor record · 2026-11-02 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a19a62-cb4f-7003-bff3-8fd124c8ad87
score
0
malicious
false
result_at
2026-11-02T04:30:13Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-11-02 05:30:13","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: 1 field

Observed: · Retrieved:

Report ID

03ec8375-7cfe-48cf-b1eb-7d12e260d226
Original source fields · JSON
Uuid
03ec8375-7cfe-48cf-b1eb-7d12e260d226

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-11-02T04:11:13Z

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
10
analyzed_at
2026-11-02T04:11:13Z
source_timestamp
2026-11-02 05:11:13
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
positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev UOMP TOPUP capture
ai_description
PhishDestroy records the captured UOMP TOPUP page on positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev, showing a mostly empty canvas with a support widget.
ai_summary
The captured page on positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev carries the title UOMP TOPUP and presents a mostly empty light-colored canvas. The only visible element is a circular purple support widget in the lower-right corner, showing a headset icon that suggests a customer-support entry point. No other content, forms or text appear in the capture, so the page's intended top-up interaction is not visible here. The stored VirusTotal domain result reports 5 detections out of 92 engines. VIPRE reported "phishing"; Webroot reported "malicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-02 04:55:28
revision
ff9b772ee5d28f56c3d80143d80cffbbd9b796a1ca09b62d025c0fbd218a6a6a
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: 20 fields

CAA records

Domain
positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Page title and metadata

Page title
UOMP TOPUP

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
3
TLS
23
Waiting
93
Connection
12
Download
15287
Response time, ms
15418

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
10485760
CO₂, grams
0.3835
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    1.13.76.55
    Host
    ns3.dnsv2.com
  • IP address
    49.7.107.155
    Host
    ns4.dnsv2.com
DNS zone
edgeone.dev

Location

IP address
43.174.246.29
ASN
139341
Organization
ACE
Country
SG

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
edgeone.dev

DNS records

A
  • 43.174.247.29
  • 43.174.246.29
CNAME
  • 2354db541df20c20.edgeone.dev.pages.dnsoe6.com

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
43.174.247.29
IP version
4

Redirects

Redirect chain
  • https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev

Page links

External link addresses
  • https://t.me/uomptopup
External links
1

HTTP headers

Response headers
Server
edgeone makers
Content-type
text/html
Original source fields · JSON
Caa records
{
    "domain": "positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-02T03:54:13Z",
    "first": "2026-11-02T03:54:13Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 12938650
}
Page title and metadata
{
    "title": "UOMP TOPUP"
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 23,
        "wait": 93,
        "connect": 12,
        "download": 15287
    },
    "response_ms": 15418
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 10485760,
    "co2_grams": 0.3835,
    "cleaner_than": 1
}
Dns server
{
    "ns": [
        {
            "ip": "1.13.76.55",
            "host": "ns3.dnsv2.com"
        },
        {
            "ip": "49.7.107.155",
            "host": "ns4.dnsv2.com"
        }
    ],
    "zone": "edgeone.dev"
}
Location
{
    "ip": "43.174.246.29",
    "asn": "139341",
    "org": "ACE",
    "country": "SG"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "edgeone.dev"
}
DNS records
{
    "A": [
        "43.174.247.29",
        "43.174.246.29"
    ],
    "CNAME": [
        "2354db541df20c20.edgeone.dev.pages.dnsoe6.com"
    ]
}
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": "43.174.247.29",
    "family": 4
}
Redirects
{
    "chain": [
        "https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev"
    ]
}
Page links
{
    "external": [
        "https://t.me/uomptopup"
    ],
    "external_count": 1
}
HTTP headers
{
    "headers": {
        "server": "edgeone makers",
        "content-type": "text/html"
    }
}

Questions about positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev

Is positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev legit?

PhishDestroy rates positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev as critical risk (80/100) from the recorded evidence; it was first recorded on 2026-11-02. Stored VirusTotal result: 5/92 engines flagged. malicious: 5. suspicious: 0. Analysis time (as stored): 2026-10-19T10:10:48Z. Retrieved (as stored): 2026-11-02T03:53:32Z. Treat the site as unsafe.

Is positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev safe to connect a wallet?

This report does not record which wallet requests positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.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 positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.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

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/uomptopupStored page reference

IoC extraction recorded 2026-11-02 05:00:08 UTC

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

URLScan · 2026-11-02 1 / 3 Used in the analysis Source file SHA-256: 92225c6ce519eed961e3079d1f49f121380b7891159000f1aec9e517acd3a9c2 SHA-256 of the prepared copy given to the model: 61e3d0f645f436e273fd445ff50781704c71192f8e602a452837ab690dd4b788
SourceURLScan · 2026-11-02
Recorded
StateStored capture
HTTP status200
Final URLhttps://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)
Observed page title
UOMP TOPUP
Automated brand references
Facebook Gmail Google Telegram
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 43 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 83 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Reputation Singapore43.174.246.29 abuse score 8/100 3 reports PhishingBad Web BotExploited Host checked Nov 2, 2026 last reported
Registrar (base domain) Tencent Cloud
Abuse contactas139341_abuse@aceville.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for edgeone.dev →
Hosting abuse contact as139341_abuse@aceville.net ACE · AS139341
Registration (base domain)edgeone.dev · Created Jun 9, 2025
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
DOM Analysisanalyzed Nov 2, 2026score 10/1004 brand signals
IoC Extractionscanned Nov 2, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
ICANN OVERSIGHT Registration: edgeone.dev

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain edgeone.dev 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
Singapore43.174.246.29
Network ASN
AS139341
Organization
ACE
Observed location
SingaporeSG
Server header
edgeone makers

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-17 02:52:54
Valid until
2026-12-16 02:52:53
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6d538285ba8e76e272733030941a0f13d96a5ad70d8ff34789947928afe7b1fa
Certificate names · 2 SANs
  • *.edgeone.dev
  • edgeone.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 · 43.174.246.29rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed
Gridinsoft
SOCRadar
VIPRE
Webroot
Yandex Safebrowsing

Archived Evidence

Wayback Machine Snapshot
View Archive
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://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
Final URL: https://positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev/
UOMP TOPUP
Response
HTTP 200
HTML body
16.53 MB
Compressed
12.31 MB
Links
0 internal · 2 external
Detected technologies
vue
Selected response headers
Content-Type: text/html
Cache-Control: public,max-age=0,must-revalidate
Content-Encoding: gzip
Server: edgeone makers
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 15
Accept-Ranges
bytes
Age
1189146
Cache-Control
public,max-age=0,must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Length
12933815
Content-Type
text/html
Date
Mon, 02 Nov 2026 03:54:31 GMT
EO-Cache-Status
Cache Hit
EO-LOG-UUID
6634048882735101287
Etag
"3735c2a93262c280167ae83d5f4a43d7"
Last-Modified
Mon, 19 Oct 2026 09:11:02 GMT
Server
edgeone makers
Vary
Origin, Access-Control-Request-Headers, Access-Control-Request-Method
X-NWS-LOG-UUID
6634048882735101287

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: 7 SHA-256 hashes: 6 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-02 03:54 UTC.

Open this scan on URLScan 01a19a62-cb4f-7003-bff3-8fd124c8ad87 ↗

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

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
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 04:53:11.000000
    Evidence SHA-256
    84dbb55eb24467752210d3ac6e951d89aefe776c7a860f0688c4beb41ec710d1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 04:53:11
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 04:53:11.000000
    Evidence SHA-256
    84dbb55eb24467752210d3ac6e951d89aefe776c7a860f0688c4beb41ec710d1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 04:53:11
    Evidence reason

Threat Response Pipeline

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

Recorded events: 10. 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
    positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Gmail · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 83
  • 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: 5/92
  • Automated brand label: Gmail
    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

4 entries
  1. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

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

positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 5 det. 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?

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 positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.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.

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/positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.dev"
  title="PhishDestroy threat report for positive-teal-bfpxnkss-dp1tgn4aeayb.edgeone.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>