Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 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
myservicesona.shop favicon

myservicesona.shop

In short

myservicesona.shop is a blocklisted domain detected by PhishDestroy on 2026-10-26.

“Welcome to OpenResty!”

Registrar
United StatesDynadot
Resolved IP
United States43.166.131.150Aceville Pte.ltd
Registered
Oct 16, 2026
First observed
Oct 26, 2026
PhishDestroy assessment Critical
86/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 1/92 Scam type: Impersonation Young domain: 10 days old
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 77
Page captures
open gallery
Domain age
Reports sent
view timeline
OTX: 3 refs Oct 26, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

myservicesona.shop is a blocklisted domain detected by PhishDestroy on 2026-10-26. Risk: critical (86/100). Registrar: Dynadot. Status: Last known active. Hosting: Aceville Pte.ltd. PhishDestroy sent 1 abuse report. VirusTotal: 1/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
1 / 92
Scam type
Impersonation
Hosting
United States43.166.131.150Aceville Pte.ltd
Registrar
United StatesDynadot
Registered
Oct 16, 2026
OTX
3 community refs
Page captures
5

PhishDestroy threat report

Overview

The captured screenshot dated 2026-10-26 shows a green welcome page headed Welcome to OpenResty!, offering documentation, support, a YouTube channel and blog buttons, product cards for OpenResty XRay and OpenResty Edge, and a row of blog thumbnails. PhishDestroy listed the domain after intake on 2026-10-26 under a young-domain rule, with first seen 2026-10-26 and registration recorded on 2026-10-16.

How the scam works

The page trades on the OpenResty name, presenting official-looking product and blog material so that a ten-day-old domain appears established and trustworthy. As a category risk, brand-lure landing pages can stage redirects or later swap in credential, download or payment forms while the domain builds reputation. No credential form was visible in this capture, so the observed stage is brand-lure staging rather than a data-entry point.

Evidence

The screenshot shows the OpenResty welcome heading, product cards, blog thumbnails and outbound brand buttons, with no login or payment form present. On 2026-10-26 the urlscan ML engine scored it malicious at 77 while its overall verdict stayed non-malicious, and the captured scan followed a redirect chain ending at a query path on myservicesona.shop. VirusTotal did not flag the domain, with Gridinsoft labelling it suspicious; Google Safe Browsing did not flag it; Spamhaus did not list it; external blocklists recorded none while the PhishDestroy internal blocklist flagged it; OTX recorded 3 pulses. Site inspection found a canvas runner game script stack (createCanvas, RunnerClasses, decodeBase64ToArrayBuffer) instead of a mainstream UI framework, 1 tracker request, and stored capture hashes for pivoting such as 4dc56440ea94.

Infrastructure

Notable weaknesses lead: CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP and CORP are all absent; DNSSEC is unsigned; SPF lookups are zero with no DKIM or DMARC evidence. TLS 1.3 with TLS_AES_256_GCM_SHA384, forward secrecy and ALPN h2; CAA records present. Registration was recorded through Dynadot Inc. on 2026-10-16, the recorded hosting network was Aceville Pte.ltd, and no WAF was identified.

What to do

If you entered credentials or personal data after visiting, change that password on the genuine service, enable 2FA, and watch for follow-up messages. Security teams should block the exact domain myservicesona.shop, retain the recorded capture hashes for pivoting, and alert on the young-domain brand-lure pattern.

Source evidenceVirusTotal 1 / 92 · OTX 3 references 9 sources

VirusTotal

1 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
0
Suspicious
1
Undetected
38

Vendor labels

Gridinsoft
suspicious

Reputation score

0

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    43.166.131.150
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.myservicesona.shop
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net

DNS records observed

JARM fingerprint

28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d

Certificate

Subject alternative names
  • myservicesona.shop
Issuer
Let's Encrypt / YE2
Serial
55de8fad3c7329715025f1c05990f43581b
SHA-256
33337e435f7a0bb410552860667e87ff35a4eb587e49bcb3642f1f4a39924df1
Subject
myservicesona.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 1,
    "undetected": 38
}
Vendor labels
{
    "Gridinsoft": "suspicious"
}
Reputation
0
First seen
2026-10-16T05:54:48Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "43.166.131.150"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.myservicesona.shop",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    }
]
Dns at
2026-10-18T16:21:41Z
Jarm
28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "myservicesona.shop"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "55de8fad3c7329715025f1c05990f43581b",
    "sha256": "33337e435f7a0bb410552860667e87ff35a4eb587e49bcb3642f1f4a39924df1",
    "subject": "myservicesona.shop",
    "valid_to": "2027-01-14T04:43:32Z",
    "valid_from": "2026-10-16T04:43:33Z"
}
Separate source record · 0 malicious + 1 suspicious / 92 · 2026-10-18 15:48:21 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-18T15:48:21Z
fetched_at
2026-10-26T12:52:00Z
stats
{"timeout":0,"harmless":53,"malicious":0,"suspicious":1,"undetected":38}

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

df4fcd31-20c2-4983-90d3-d47012dacbd6

Final URL

https://myservicesona.shop/

HTTP response

200

Navigation history

  • URL
    https://myservicesona.shop/
    Status
    200

DOM structure hash

e9a2a70d82f470082608dd2ee9b5df20f86cad11160536bf283f057edbc7a278

Document hash

8d374d23d4bc454767b8d4eeda8c3020a4f878a29207e31d74f6a1e55d4b7c4b

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    myservicesona.shop
    Type
    A
    Value
    43.166.131.150

DNSSEC valid

No

IP address

43.166.131.150
Original source fields · JSON
Uuid
df4fcd31-20c2-4983-90d3-d47012dacbd6
Final url
https://myservicesona.shop/
Status
200
History
[
    {
        "url": "https://myservicesona.shop/",
        "status": 200
    }
]
DOM structure hash
e9a2a70d82f470082608dd2ee9b5df20f86cad11160536bf283f057edbc7a278
Document hash
8d374d23d4bc454767b8d4eeda8c3020a4f878a29207e31d74f6a1e55d4b7c4b
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "myservicesona.shop",
        "type": "A",
        "value": "43.166.131.150"
    }
]
Dnssec valid
false
Ip
43.166.131.150

URLScan

Malicious · engine verdict · score 77

Open report
URLScanOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

01a17824-ae9b-73c8-a59b-a00fef7879ee

Final URL

https://myservicesona.shop/query/a_index.html

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

8

Registered domain age, days

8

Page requests

8

Provider verdicts

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

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a17824-ae9b-73c8-a59b-a00fef7879ee
Final url
https://myservicesona.shop/query/a_index.html
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
8
Apex age days
8
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 77,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a17824-ae9b-73c8-a59b-a00fef7879ee
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

86 / 100 · heuristic score · 0 brand references · 1 classification

Open report
Separate monitor score · 0 / 100 · 2026-10-26T12:55:27Z

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
0
analyzed_at
2026-10-26T12:55:27Z
source_timestamp
2026-10-26 13:55:27
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
myservicesona.shop — OpenResty Impersonation Landing Page
ai_description
PhishDestroy assesses myservicesona.shop as an OpenResty-impersonation landing page posing a brand-lure risk to visitors.
ai_generated_at
2026-10-26T20:15:50Z
ai_generated_by
mimo-flash
interpretation
Narrative generation metadata, separate from provider observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
myservicesona.shop

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Page title and metadata

Page title
Welcome to OpenResty!

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
289
TLS
134
Waiting
211
Connection
191
Download
208
Response time, ms
1033

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

Carbon estimate

Bytes
128646
CO₂, grams
0.0047
Cleaner than, %
16

DNS servers

Nameservers
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
DNS zone
myservicesona.shop

Location

IP address
43.166.131.150
ASN
132203
Organization
Aceville Pte.ltd
City
Ashburn
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
myservicesona.shop

DNS records

A
  • 43.166.131.150
NS
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.myservicesona.shop
Serial
2026101901
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

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.166.131.150
IP version
4

Redirects

Redirect chain
  • https://myservicesona.shop

Page links

External link addresses
  • https://openresty.org/
  • https://openresty.com/
  • https://www.youtube.com/channel/UCXVmwF-UCScv2ftsGoMqxhw
  • https://blog.openresty.com/
  • https://openresty.com/en/xray/
  • https://openresty.com/en/edge/
  • https://blog.openresty.com/en/xray-azure/
  • https://blog.openresty.com/en/ysql-count-ngx-reqs/
  • https://blog.openresty.com/en/edge-enable-waf/
  • https://blog.openresty.com/en/edge-edgelang/
  • https://blog.openresty.com/en/edge-upstream-real-ip/
External links
11

HTTP headers

Response headers
Server
openresty/1.31.1.1
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "myservicesona.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-26T12:18:24Z",
    "first": "2026-10-16T14:26:26Z",
    "changes": 0,
    "days_archived": 2,
    "scans_per_day": 0.1,
    "avg_page_bytes": 46281
}
Page title and metadata
{
    "title": "Welcome to OpenResty!"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 289,
        "tls": 134,
        "wait": 211,
        "connect": 191,
        "download": 208
    },
    "response_ms": 1033
}
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": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 128646,
    "co2_grams": 0.0047,
    "cleaner_than": 16
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "myservicesona.shop"
}
Location
{
    "ip": "43.166.131.150",
    "asn": "132203",
    "org": "Aceville Pte.ltd",
    "city": "Ashburn",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "myservicesona.shop"
}
DNS records
{
    "A": [
        "43.166.131.150"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.myservicesona.shop\", \"serial\": 2026101901, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
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.166.131.150",
    "family": 4
}
Redirects
{
    "chain": [
        "https://myservicesona.shop"
    ]
}
Page links
{
    "external": [
        "https://openresty.org/",
        "https://openresty.com/",
        "https://www.youtube.com/channel/UCXVmwF-UCScv2ftsGoMqxhw",
        "https://blog.openresty.com/",
        "https://openresty.com/en/xray/",
        "https://openresty.com/en/edge/",
        "https://blog.openresty.com/en/xray-azure/",
        "https://blog.openresty.com/en/ysql-count-ngx-reqs/",
        "https://blog.openresty.com/en/edge-enable-waf/",
        "https://blog.openresty.com/en/edge-edgelang/",
        "https://blog.openresty.com/en/edge-upstream-real-ip/"
    ],
    "external_count": 11
}
HTTP headers
{
    "headers": {
        "server": "openresty/1.31.1.1",
        "content-type": "text/html"
    }
}

Questions about myservicesona.shop

Is myservicesona.shop legit?

No. PhishDestroy classifies myservicesona.shop as a blocklisted domain (risk: critical, 86/100); it was first detected on 2026-10-26. VirusTotal: 1/92 engines flag it. Treat the site as unsafe.

Is myservicesona.shop safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on myservicesona.shop. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used myservicesona.shop?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

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

Last checked

Stored Capture · 5 captures

All capture links and hashes (5)
Observed page title
Welcome to OpenResty!
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 79 days
myservicesona.shop: caution — 1/92 VirusTotal engines. PhishDestroy risk score 86/100 (critical).
Social preview card myservicesona.shop: caution — 1/92 VirusTotal engines. PhishDestroy risk score 86/100 (critical). v 8797149fd718

Domain details

Domain
IP Reputation United States43.166.131.150 abuse score 0/100 0 reports checked Oct 26, 2026 last reported
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationCreated Oct 16, 2026 (10d · Very New!) — Expires Oct 16, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 86/100
Submitted URLhttps://myservicesona.shop/query/a_index.html
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, 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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States43.166.131.150
Network ASN
AS132203
Organization
Aceville Pte.ltd
Observed location
United StatesAshburn, US
Server header
openresty/1.31.1.1

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.myservicesona.shop
  • serial: 2026101901
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-16 04:43:33
Valid until
2027-01-14 04:43:32
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint33337e435f7a0bb410552860667e87ff35a4eb587e49bcb3642f1f4a39924df1
Certificate names · 1 SAN
  • myservicesona.shop

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

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
Gridinsoft

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of myservicesona.shop · checked Oct 26, 2026

100
Good
Performance
FCP
1.27 s
First Contentful Paint
LCP
1.27 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.27 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 403
Requested URL: https://myservicesona.shop/query/a_index.html
Access Denied
Response
HTTP 403
HTML body
645 B
Compressed
406 B
Links
0 internal · 0 external
Selected response headers
Server: openresty/1.31.1.1
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 7
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 26 Oct 2026 12:18:11 GMT
Server
openresty/1.31.1.1
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

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.

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-10-26 13:18:00.000000
    Evidence SHA-256
    62729208ff6a34efeb231051bd6fec2ab1c60938b3657ee27e4609996fefbc24
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:18:00
    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-10-26 13:18:00.000000
    Evidence SHA-256
    62729208ff6a34efeb231051bd6fec2ab1c60938b3657ee27e4609996fefbc24
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:18:00
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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
    myservicesona.shop detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · 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: 77
  • 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: 1/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Tencent. Abuse contacts: 1.
    • abuse@tencent.com
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

6 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    1/92 engine detections

    View source
  3. Abuse report sent

    PD-20261026-B96167 · Receipt 83444

    abuse@tencent.com
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    myservicesona.shop

    View source
  6. URLScan

    Page captured

    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.

Check for cloaking

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

myservicesona.shop

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-B96167 Recipient: abuse@tencent.com
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records 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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 myservicesona.shop)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/myservicesona.shop"
  title="PhishDestroy threat report for myservicesona.shop"
  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>