Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 10/92 engines flagged. malicious: 9. suspicious: 1. Analysis time (as stored): 2026-10-26T06:15:01Z. Retrieved (as stored): 2026-10-26T16:17:52Z. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
turingex.world favicon

turingex.world

In short

PhishDestroy first recorded turingex.world on 2026-10-26. Stored VirusTotal result: 10/92 engines flagged. malicious: 9. suspicious: 1. Analysis time (as stored): 2026-10-26T06:15:01Z. Retrieved (as stored): 2026-10-26T16:17:52Z. Listed by external blocklists: MetaMask, SEAL.

“Turing”

Review the evidence
Registrar
Amazon
Resolved IP
Singapore5.199.166.153LIX
Registered
Sep 15, 2025
First observed
Oct 26, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 10/92 Stored blocklist matches: 2
VirusTotal
10 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
Page captures
7
open gallery
Domain age
413 days
registered 2025-09-15 according to WHOIS
Reports sent
1
view timeline
Oct 26, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is trustandsafety@support.aws.com. The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
7 days
Reports sent
1
Latest case ID
PD-20261026-371636
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded turingex.world on 2026-10-26. Stored VirusTotal result: 10/92 engines flagged. malicious: 9. suspicious: 1. Analysis time (as stored): 2026-10-26T06:15:01Z. Retrieved (as stored): 2026-10-26T16:17:52Z. Listed by external blocklists: MetaMask, SEAL. Risk: critical (100/100). Registrar: Amazon. Status: Last known active. Hosting: LIX. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
10 / 92
Blocklist matches
2
Hosting
Singapore5.199.166.153LIX
Registrar
Amazon
Registered
Sep 15, 2025
Page captures
7
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for turingex.world. 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 10 / 92 8 sources

VirusTotal

10 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
9
Suspicious
1
Undetected
34

Vendor labels

ESET
phishing
G-Data
phishing
Sophos
phishing
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
suspicious

Reputation score

0

Categories

Sophos
phishing and fraud
alphaMountain.ai
Suspicious (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns-469.awsdns-58.com
  • TTL, seconds
    900
    Type
    SOA
    Responsible mailbox
    awsdns-hostmaster.amazon.com
    Value
    ns-801.awsdns-36.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns-1338.awsdns-39.org
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns-1545.awsdns-01.co.uk
  • TTL, seconds
    60
    Type
    A
    Value
    5.199.166.153
  • TTL, seconds
    600
    Type
    MX
    Value
    inbound-smtp.us-east-1.amazonaws.com
    Priority
    10
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns-801.awsdns-36.net

DNS records observed

JARM fingerprint

3fd3fd0003fd3fd21c42d42d000000bdfc58c9a46434368cf60aa440385763

Certificate

Subject alternative names
  • turingex.world
  • www.turingex.world
Issuer
Let's Encrypt / YR2
Serial
5d7ac29717db782a1568aac5a0fd5b0ba46
SHA-256
dd95d448a46ce68dcb4801452dcbca515ad70ab7cd236246b88cc45891e2a2b7
Subject
turingex.world
Valid until
Valid from

Registry data (RDAP)

Status
  • active
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
Amazon Registrar, Inc.
Registrar IANA ID
468
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 9,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Suspicious (alphaMountain.ai)"
}
Created
2025-09-15T00:00:00Z
Updated
2025-09-15T00:00:00Z
First seen
2025-09-16T09:04:24Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-469.awsdns-58.com"
    },
    {
        "ttl": 900,
        "type": "SOA",
        "rname": "awsdns-hostmaster.amazon.com",
        "value": "ns-801.awsdns-36.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-1338.awsdns-39.org"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-1545.awsdns-01.co.uk"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "5.199.166.153"
    },
    {
        "ttl": 600,
        "type": "MX",
        "value": "inbound-smtp.us-east-1.amazonaws.com",
        "priority": 10
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-801.awsdns-36.net"
    }
]
Dns at
2026-10-26T06:15:20Z
Jarm
3fd3fd0003fd3fd21c42d42d000000bdfc58c9a46434368cf60aa440385763
Certificate
{
    "san": [
        "turingex.world",
        "www.turingex.world"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5d7ac29717db782a1568aac5a0fd5b0ba46",
    "sha256": "dd95d448a46ce68dcb4801452dcbca515ad70ab7cd236246b88cc45891e2a2b7",
    "subject": "turingex.world",
    "valid_to": "2026-12-08T19:25:50Z",
    "valid_from": "2026-09-09T19:25:51Z"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-09-15T09:59:01Z",
        "last changed": "2026-10-24T09:30:21Z",
        "registration": "2025-09-15T09:59:01Z",
        "registrar expiration": "2027-09-15T09:59:01Z",
        "last update of RDAP database": "2026-10-25T05:48:09Z"
    },
    "registrar": "Amazon Registrar, Inc.",
    "registrar_iana_id": "468"
}
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
10
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","ESET","Fortinet","G-Data","Gridinsoft","Kaspersky","LevelBlue","SOCRadar","Sophos"]
observed_at
2026-10-26 06:15:01
checked_at
2026-10-26 17:17:59
fetched_at
2026-10-26 16:18:00
time_basis
as stored; legacy timezone not established

URLScan

Malicious

SHA-256 065f3fedb8b22dedf9d717407f0eb313b301ec50b1d2f4bd299451484a186034

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1790c-bc35-72a6-aaf5-2cc5d33003f4

Final URL

https://turingex.world/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://turingex.world/
    From
    http://turingex.world/
    Status
    307

IP address

5.199.166.153

Reverse DNS (PTR)

ip-5-199-166-153.004.ptr.cherryservers.net

Contacted domains

  • tongji.dcloud.io
  • turingex.cc
  • cdn.dcloud.net.cn

Contacted IP addresses

  • 43.152.26.151
  • 5.199.166.153

Autonomous systems (ASN)

  • 139341
  • 216444

Server countries

  • SG

Document hash

c12779116f7b318e24948a43c4be83b45c564622f545ca368a900214812abfd9

Script hashes

  • 5181f8561ea7bc96b34efdd81b736ee41e4949457eac4eb8c1fa9a2ff59b7afe
  • 700452dfa1f9841a07c44484afb5d0d46b036555ff129a647a05e989e09beacb
  • a2715b512d97d70154bab01d70e960d27a89e519e2ffdd683ee539633fac3097
  • cdce5486ed708fa4fbc8a3fd123a2fdf98c3b98e953b8554f32bd549786aaaf9
  • 36ffda4ca14a207b8b2ae9e8b5e1d4e189a922c63f93c65766c8fb92ca3ef727

JavaScript globals

  • coverSupport
  • webpackJsonp
  • __uniConfig
  • __uniRoutes
  • UniApp
  • UniViewJSBridge
  • UniServiceJSBridge
  • uni
  • wx
  • getApp
  • getCurrentPages
  • __webSocket

Browser storage keys

  • __DC_STAT_UUID
  • $$STAT__DBDATA:__UNI__6B2B303
  • theme
  • _STAT_LAST_PAGE_ROUTE
  • Report_Data_Time
  • Report_Status

TLS session and certificate

Subject alternative names
  • turingex.world
  • www.turingex.world
Cipher
AES_256_GCM
Issuer
YR2
Subject
turingex.world
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

405

Registered domain age, days

405

Certificate age, days

46

Certificate validity, days

89

Page requests

49

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • generic
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Generic
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a1790c-bc35-72a6-aaf5-2cc5d33003f4
Final url
https://turingex.world/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://turingex.world/",
        "from": "http://turingex.world/",
        "status": 307
    }
]
Ip
5.199.166.153
Ptr
ip-5-199-166-153.004.ptr.cherryservers.net
Contacted domains
[
    "tongji.dcloud.io",
    "turingex.cc",
    "cdn.dcloud.net.cn"
]
Contacted IP addresses
[
    "43.152.26.151",
    "5.199.166.153"
]
Asns
[
    "139341",
    "216444"
]
Countries
[
    "SG"
]
Document hash
c12779116f7b318e24948a43c4be83b45c564622f545ca368a900214812abfd9
Script hashes
[
    "5181f8561ea7bc96b34efdd81b736ee41e4949457eac4eb8c1fa9a2ff59b7afe",
    "700452dfa1f9841a07c44484afb5d0d46b036555ff129a647a05e989e09beacb",
    "a2715b512d97d70154bab01d70e960d27a89e519e2ffdd683ee539633fac3097",
    "cdce5486ed708fa4fbc8a3fd123a2fdf98c3b98e953b8554f32bd549786aaaf9",
    "36ffda4ca14a207b8b2ae9e8b5e1d4e189a922c63f93c65766c8fb92ca3ef727"
]
Globals
[
    "coverSupport",
    "webpackJsonp",
    "__uniConfig",
    "__uniRoutes",
    "UniApp",
    "UniViewJSBridge",
    "UniServiceJSBridge",
    "uni",
    "wx",
    "getApp",
    "getCurrentPages",
    "__webSocket"
]
Storage keys
[
    "__DC_STAT_UUID",
    "$$STAT__DBDATA:__UNI__6B2B303",
    "theme",
    "_STAT_LAST_PAGE_ROUTE",
    "Report_Data_Time",
    "Report_Status"
]
Tls
{
    "san": [
        "turingex.world",
        "www.turingex.world"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "turingex.world",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-08T19:25:50Z",
    "valid_from": "2026-09-09T19:25:51Z"
}
Domain age days
405
Apex age days
405
Tls age days
46
Tls valid days
89
Requests
49
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "generic"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Generic"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
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
01a17165-8e2d-76ae-bbf8-63f2a321c722
score
null
malicious
null
result_at
null
enriched_at
2026-10-27T09:20:17Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-27 10:20:17"}
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: 10 fields

Observed: · Retrieved:

Report ID

c8bfe90a-8c8f-4967-b215-eca856b2b1d8

Final URL

https://turingex.world/

HTTP response

200

Navigation history

  • URL
    https://turingex.world/
    Status
    200

DOM structure hash

2882b8036784a0ac5de4826536992b2d33e87b04a401c78880374941370b62ad

Document hash

c12779116f7b318e24948a43c4be83b45c564622f545ca368a900214812abfd9

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    turingex.world
    Type
    A
    Value
    5.199.166.153

DNSSEC valid

No

IP address

5.199.166.153
Original source fields · JSON
Uuid
c8bfe90a-8c8f-4967-b215-eca856b2b1d8
Final url
https://turingex.world/
Status
200
History
[
    {
        "url": "https://turingex.world/",
        "status": 200
    }
]
DOM structure hash
2882b8036784a0ac5de4826536992b2d33e87b04a401c78880374941370b62ad
Document hash
c12779116f7b318e24948a43c4be83b45c564622f545ca368a900214812abfd9
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "turingex.world",
        "type": "A",
        "value": "5.199.166.153"
    }
]
Dnssec valid
false
Ip
5.199.166.153

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

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: 21 fields

Mail configuration

MX records
  • inbound-smtp.us-east-1.amazonaws.com
SPF lookups
0

CAA records

Domain
turingex.world

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Page title and metadata

Page title
Turing

Trackers

Requests
32

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
3
TLS
169
Waiting
160
Connection
173
Download
0
Response time, ms
505

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443
  • 3306

Carbon estimate

Bytes
783
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    205.251.198.9
    Host
    ns-1545.awsdns-01.co.uk
  • IP address
    205.251.193.213
    Host
    ns-469.awsdns-58.com
  • IP address
    205.251.195.33
    Host
    ns-801.awsdns-36.net
  • IP address
    205.251.197.58
    Host
    ns-1338.awsdns-39.org
DNS zone
turingex.world

Location

IP address
5.199.166.153
ASN
216444
Organization
LIX
City
Singapore
Country
SG

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
turingex.world

DNS records

A
  • 5.199.166.153
MX
  • Mail server
    inbound-smtp.us-east-1.amazonaws.com
    Priority
    10
NS
  • ns-801.awsdns-36.net
  • ns-1338.awsdns-39.org
  • ns-469.awsdns-58.com
  • ns-1545.awsdns-01.co.uk
SOA
Primary nameserver
ns-801.awsdns-36.net
Hostmaster
awsdns-hostmaster.amazon.com
Serial
1
Refresh, seconds
7200
Retry, seconds
900
Expiry, seconds
1209600
Minimum TTL, seconds
86400

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

HTTP security policies

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

IP lookup

IP address
5.199.166.153
IP version
4

Redirects

Redirect chain
  • https://turingex.world

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Mail configuration
{
    "mx": [
        "inbound-smtp.us-east-1.amazonaws.com"
    ],
    "spf_lookups": 0
}
Caa records
{
    "domain": "turingex.world"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-26T16:19:54Z",
    "first": "2026-10-26T16:19:54Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1036
}
Page title and metadata
{
    "title": "Turing"
}
Trackers
{
    "requests": 32
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 169,
        "wait": 160,
        "connect": 173,
        "download": 0
    },
    "response_ms": 505
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443,
        3306
    ]
}
Carbon
{
    "bytes": 783,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.198.9",
            "host": "ns-1545.awsdns-01.co.uk"
        },
        {
            "ip": "205.251.193.213",
            "host": "ns-469.awsdns-58.com"
        },
        {
            "ip": "205.251.195.33",
            "host": "ns-801.awsdns-36.net"
        },
        {
            "ip": "205.251.197.58",
            "host": "ns-1338.awsdns-39.org"
        }
    ],
    "zone": "turingex.world"
}
Location
{
    "ip": "5.199.166.153",
    "asn": "216444",
    "org": "LIX",
    "city": "Singapore",
    "country": "SG"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "turingex.world"
}
DNS records
{
    "A": [
        "5.199.166.153"
    ],
    "MX": [
        "{\"exchange\": \"inbound-smtp.us-east-1.amazonaws.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns-801.awsdns-36.net",
        "ns-1338.awsdns-39.org",
        "ns-469.awsdns-58.com",
        "ns-1545.awsdns-01.co.uk"
    ],
    "SOA": "{\"nsname\": \"ns-801.awsdns-36.net\", \"hostmaster\": \"awsdns-hostmaster.amazon.com\", \"serial\": 1, \"refresh\": 7200, \"retry\": 900, \"expire\": 1209600, \"minttl\": 86400}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "5.199.166.153",
    "family": 4
}
Redirects
{
    "chain": [
        "https://turingex.world"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about turingex.world

Is turingex.world legit?

PhishDestroy rates turingex.world as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 10/92 engines flagged. malicious: 9. suspicious: 1. Analysis time (as stored): 2026-10-26T06:15:01Z. Retrieved (as stored): 2026-10-26T16:17:52Z. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is turingex.world safe to connect a wallet?

This report does not record which wallet requests turingex.world 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 turingex.world?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 7 captures

Stored capture 1 / 7
SourceStored capture
Recorded
StateStored capture
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)
Observed page title
Turing
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 35 days
turingex.world: Crypto scam — Blocked by MetaMask, flagged by SEAL, 10/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card turingex.world: Crypto scam — Blocked by MetaMask, flagged by SEAL, 10/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v db023bcd23b4

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Reputation Singapore5.199.166.153 abuse score 0/100 0 reports checked Oct 26, 2026
Registrar Amazon
Abuse contactabuse@cherryservers.com, trustandsafety@support.aws.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for turingex.world →
RegistrationCreated Sep 15, 2025 — Expires Sep 15, 2027
Registrant countryUnited Kingdom VirusTotal WHOIS
Registrant807b77595b794db5 VirusTotal WHOIS
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 95/100
Submitted URLhttp://turingex.world/
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.

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
Singapore5.199.166.153
Network ASN
AS216444
AS name
CHERRYSERVERS4-AS UAB "Cherry Servers", LT
Organization
LIX
Observed location
SingaporeSingapore, SG
Server header
nginx

Nameservers 4

  • ns-1338.awsdns-39.org
  • ns-1545.awsdns-01.co.uk
  • ns-469.awsdns-58.com
  • ns-801.awsdns-36.net

SOA

  • nsname: ns-801.awsdns-36.net
  • hostmaster: awsdns-hostmaster.amazon.com
  • serial: 1
  • refresh: 7200
  • retry: 900
  • expire: 1209600
  • minttl: 86400

Mail routing 1 MX record

  • inbound-smtp.us-east-1.amazonaws.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-09 19:25:51
Valid until
2026-12-08 19:25:50
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintdd95d448a46ce68dcb4801452dcbca515ad70ab7cd236246b88cc45891e2a2b7
Certificate names · 2 SANs
  • turingex.world
  • www.turingex.world

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

viewdns.info · 5.199.166.153rapiddns.io

Latest Classified Outcome 2026-11-02 11:51:35 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-02 11:51:35 UTC
RDAP registration
Observed timeline last reachable: 2026-11-02 23:22:03 UTC last content: 2026-11-02 11:51:35 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains5

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • eijthdb5wytpssbe.turingex.worldDomain record
  • qwert.turingex.worldDomain record
  • rnhcsw4mkbwfsk55.turingex.worldDomain record
  • test123.turingex.worldDomain record
  • www.turingex.worldDomain record
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 92 security vendors flagged this domain
View on VT
Last analyzed
ESET
G-Data
Sophos
Fortinet
SOCRadar
Kaspersky
LevelBlue
Gridinsoft
BitDefender
alphaMountain.ai
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of turingex.world · checked Oct 26, 2026

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

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

Archived HTTP response HTTP 200
Requested URL: http://turingex.world/
Turing
Response
HTTP 200
HTML body
783 B
Compressed
481 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: f9dd75e4f6e2903571bde3066b43073c0fe6387564b469702e7ade89502ffcc8
Saved response-header values · 10
Accept-Ranges
bytes
Alt-Svc
quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"
Connection
keep-alive
Content-Length
783
Content-Type
text/html
Date
Mon, 26 Oct 2026 16:20:17 GMT
Etag
"69a64d1c-30f"
Last-Modified
Tue, 03 Mar 2026 02:53:16 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 49 SHA-256 hashes: 48 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:56 UTC.

Open this scan on URLScan 01a1790c-bc35-72a6-aaf5-2cc5d33003f4 ↗

Stored observation history6

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 1
  1. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations39

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. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  2. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-02 12:51:35.000000
    Evidence SHA-256
    4409b5c3a78c212e39707298b6d6e1e54ab3cef2d1fc86045760c293e459df30
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:51:35
    Evidence reason
    alive_content
  3. 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-02 12:51:35.000000
    Evidence SHA-256
    4409b5c3a78c212e39707298b6d6e1e54ab3cef2d1fc86045760c293e459df30
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:51:35
    Evidence reason
    alive_content
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-02 00:52:36.000000
    Evidence SHA-256
    deb7c4edfee47f62eb10803424027c530b37cb2ace700717ac14671a00888355
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:52:36
    Evidence reason
    alive_content
  5. 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-02 00:52:36.000000
    Evidence SHA-256
    deb7c4edfee47f62eb10803424027c530b37cb2ace700717ac14671a00888355
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:52:36
    Evidence reason
    alive_content
  6. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:54:59.000000
    Evidence SHA-256
    d9f9a7d4a14e6acdb576d00ea6d12c80b78a06805cf5050a8480bfdd26e47c8e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:54:59
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:54:59.000000
    Evidence SHA-256
    d9f9a7d4a14e6acdb576d00ea6d12c80b78a06805cf5050a8480bfdd26e47c8e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:54:59
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:42:55.000000
    Evidence SHA-256
    838362535e687411d94b91e2909b209472782d889242f8d752c8a3f8c749a2f3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:42:55
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:42:55.000000
    Evidence SHA-256
    838362535e687411d94b91e2909b209472782d889242f8d752c8a3f8c749a2f3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:42:55
    Evidence reason
    alive_content
  11. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  12. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:54:24.000000
    Evidence SHA-256
    00bb7ca540795455c35ce33a2542783431fccd0e6499fc85175ed69ac21808ca
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:54:24
    Evidence reason
    alive_content
  13. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:54:24.000000
    Evidence SHA-256
    00bb7ca540795455c35ce33a2542783431fccd0e6499fc85175ed69ac21808ca
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:54:24
    Evidence reason
    alive_content
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 04:36:30.000000
    Evidence SHA-256
    ee672e5810a9d0bdf0a7909111bf233e4cce7aef1e3a87cf2bd4ede97677b916
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 04:36:30
    Evidence reason
    alive_content
  15. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 04:36:30.000000
    Evidence SHA-256
    ee672e5810a9d0bdf0a7909111bf233e4cce7aef1e3a87cf2bd4ede97677b916
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 04:36:30
    Evidence reason
    alive_content
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:50:53.000000
    Evidence SHA-256
    b2659e14023aa56bd433f335eaa7419e64a52286a0d78c91cbc692a320840ff2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:50:53
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:50:53.000000
    Evidence SHA-256
    b2659e14023aa56bd433f335eaa7419e64a52286a0d78c91cbc692a320840ff2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:50:53
    Evidence reason
    alive_content
  18. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 13:01:15.000000
    Evidence SHA-256
    b52693a7b2bc174b1a0a35fe13aec20787873e0b9317d6ce42dd1da1d0c05dab
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:01:15
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 13:01:15.000000
    Evidence SHA-256
    b52693a7b2bc174b1a0a35fe13aec20787873e0b9317d6ce42dd1da1d0c05dab
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:01:15
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:59:09.000000
    Evidence SHA-256
    74b569624517e7acaaf4855f11a597a814055204b9d6d542d7b97d1887fd602f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:59:09
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:59:09.000000
    Evidence SHA-256
    74b569624517e7acaaf4855f11a597a814055204b9d6d542d7b97d1887fd602f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:59:09
    Evidence reason
    alive_content
  23. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 17:14:29.775349
    Evidence SHA-256
    db74fcc6d756cb36943e7c7745a6a8737aaa6959c4a9679405e4f75391d96929
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 17:14:29.775349
    Evidence reason
  24. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:58:42.000000
    Evidence SHA-256
    31dd8d3f689e505e11ab631ded89cad8ee6fc7903d0286248c1d89c8376365e2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:58:42
    Evidence reason
    alive_content
  25. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:58:42.000000
    Evidence SHA-256
    31dd8d3f689e505e11ab631ded89cad8ee6fc7903d0286248c1d89c8376365e2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:58:42
    Evidence reason
    alive_content
  26. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 04:38:06.000000
    Evidence SHA-256
    b5f461f41df2505e6c8d98de91451497d1a9295e9367bdbbfac24f732ba5520b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:38:06
    Evidence reason
    alive_content
  27. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 04:38:06.000000
    Evidence SHA-256
    b5f461f41df2505e6c8d98de91451497d1a9295e9367bdbbfac24f732ba5520b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:38:06
    Evidence reason
    alive_content
  28. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 00:03:10.000000
    Evidence SHA-256
    c29a125e5b57093f973ecba0a007a4605e9ff8adbd7ff6ad8fa3ff1bdce7fdf0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:03:10
    Evidence reason
    alive_content
  29. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 00:03:10.000000
    Evidence SHA-256
    c29a125e5b57093f973ecba0a007a4605e9ff8adbd7ff6ad8fa3ff1bdce7fdf0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:03:10
    Evidence reason
    alive_content
  30. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  31. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:03:55.000000
    Evidence SHA-256
    d3d215be7b057c4358f5c755b0c63cbeeca8f909f7dc4dd89e571d0130e4b9d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:03:55
    Evidence reason
    alive_content
  32. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:03:55.000000
    Evidence SHA-256
    d3d215be7b057c4358f5c755b0c63cbeeca8f909f7dc4dd89e571d0130e4b9d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:03:55
    Evidence reason
    alive_content
  33. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:22.000000
    Evidence SHA-256
    ad64cceb02833786d732cba3e99c7e05f3578582ddb427c42a916ebb8a99b508
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:04:22
    Evidence reason
    alive_content
  34. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:22.000000
    Evidence SHA-256
    ad64cceb02833786d732cba3e99c7e05f3578582ddb427c42a916ebb8a99b508
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:04:22
    Evidence reason
    alive_content
  35. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:26.000000
    Evidence SHA-256
    dc801fa37b1395a818f70d0a0a2b24b06e2b1fb7992ad54bbc43ad7328dcd93c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:04:26
    Evidence reason
    alive_content
  36. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:26.000000
    Evidence SHA-256
    dc801fa37b1395a818f70d0a0a2b24b06e2b1fb7992ad54bbc43ad7328dcd93c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:04:26
    Evidence reason
    alive_content
  37. 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 17:32:19.000000
    Evidence SHA-256
    f23cf64c9d56d957bbe1be7f33b6508004eb027cdacf753e4dcea0116839c206
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 17:32:19
    Evidence reason
  38. 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 17:32:19.000000
    Evidence SHA-256
    f23cf64c9d56d957bbe1be7f33b6508004eb027cdacf753e4dcea0116839c206
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 17:32:19
    Evidence reason
  39. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-10-26 17:18:12.960038
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. 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
    turingex.world detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 10/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • 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: Support.aws. Abuse contacts: 1.
    • trustandsafety@support.aws.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

4 entries
  1. Abuse report sent

    PD-20261026-371636 · Receipt 83485

    trustandsafety@support.aws.com
  2. URLScan

    Page captured

    View source
  3. Added to PhishDestroy

    turingex.world

    View source
  4. VirusTotal

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

turingex.world

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 10 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-371636 Recipient: trustandsafety@support.aws.com
PDF notice generated
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?

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

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 turingex.world)
  • 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/turingex.world"
  title="PhishDestroy threat report for turingex.world"
  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>