Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. malicious: 10. suspicious: 2. Analysis time (as stored): 2026-11-02T09:33:51Z. Retrieved (as stored): 2026-11-04T22:34:57Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
qntezlhu.shop favicon

qntezlhu.shop

In short

On 2026-11-04, qntezlhu.shop redirected to www.tiktok.com. The destination page displays the TikTok interface with a dark theme, showing a left sidebar with navigation items such as For You, Shop, Explore, Following, Short dramas, LIVE, Upload, Profile, and More, along with a Log in button and a search field at the top. A central overlay panel with a Skip option and a loading spinner appears over the video area, and a bottom-right notice reads that TikTok Shop is now available on web.

“TikTok - Make Your Day”

Review the evidence
Registrar
West263 International
Resolved IP
United States43.172.114.23Shenzhen Tencent Computer Systems Company Limited
Registered
Dec 6, 2025
First observed
Nov 4, 2026
PhishDestroy assessment Critical
96/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 12/92 Spamhaus DBL: phishing domain
VirusTotal
12 / 92
engine detections ·
OTX
4
community references
URLScan
Malicious
engine verdict · score 80
Page captures
4
open gallery
Domain age
333 days
registered 2025-12-06 according to WHOIS · source data differ
OTX: 4 refs Nov 4, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded qntezlhu.shop on 2026-11-04. Stored VirusTotal result: 12/92 engines flagged. malicious: 10. suspicious: 2. Analysis time (as stored): 2026-11-02T09:33:51Z. Retrieved (as stored): 2026-11-04T22:34:57Z. Risk: critical (96/100). Registrar: West263 International. Status: Last known active. Hosting: Shenzhen Tencent Computer Systems Company Limited. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
12 / 92
Hosting
United States43.172.114.23Shenzhen Tencent Computer Systems Company Limited
Registrar
West263 International
Registered
Dec 6, 2025
OTX
4 community refs
Page captures
4
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-04T22:36:26Z
SHA-256: 6a03e775d32c3e6f450f3c1a63b53c55e8aeeec9e3bb60a911b78501485b1d81

PhishDestroy analysis, reviewed version

On 2026-11-04, qntezlhu.shop redirected to www.tiktok.com. The destination page displays the TikTok interface with a dark theme, showing a left sidebar with navigation items such as For You, Shop, Explore, Following, Short dramas, LIVE, Upload, Profile, and More, along with a Log in button and a search field at the top. A central overlay panel with a Skip option and a loading spinner appears over the video area, and a bottom-right notice reads that TikTok Shop is now available on web.

The stored VirusTotal domain result reports 12 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 12 / 92 · OTX 4 references 8 sources

VirusTotal

12 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
10
Suspicious
2
Undetected
31

Vendor labels

CRDF
malicious
DNS8
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Netcraft
malicious
SOCRadar
phishing
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

First seen

DNS records

  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    dnsconct.363.hk
    Value
    ns1.363.hk
  • TTL, seconds
    900
    Type
    A
    Value
    43.172.114.23
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns4.363.hk
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.363.hk
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns3.363.hk
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.363.hk

DNS records observed

JARM fingerprint

15d3fd16d29d29d00042d43d00000041ad16ead50175e1e575f5579aa6b5c8

Certificate

Subject alternative names
  • qntezlhu.shop
Issuer
Let's Encrypt / YR2
Serial
6fdcb169c24fdf3b27d43eee4728338d8f8
SHA-256
6080a6214ca96417f91cbf9539a7710019df890c291add9c9b5453e1e74128bb
Subject
qntezlhu.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 10,
    "suspicious": 2,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
First seen
2025-12-06T14:15:43Z
DNS records
[
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "dnsconct.363.hk",
        "value": "ns1.363.hk"
    },
    {
        "ttl": 900,
        "type": "A",
        "value": "43.172.114.23"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns4.363.hk"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.363.hk"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns3.363.hk"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.363.hk"
    }
]
Dns at
2026-11-02T09:39:18Z
Jarm
15d3fd16d29d29d00042d43d00000041ad16ead50175e1e575f5579aa6b5c8
Certificate
{
    "san": [
        "qntezlhu.shop"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6fdcb169c24fdf3b27d43eee4728338d8f8",
    "sha256": "6080a6214ca96417f91cbf9539a7710019df890c291add9c9b5453e1e74128bb",
    "subject": "qntezlhu.shop",
    "valid_to": "2026-11-20T06:27:02Z",
    "valid_from": "2026-08-22T06:27:03Z"
}
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
12
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","CyRadar","DNS8","G-Data","Gridinsoft","Lionic","Netcraft","SOCRadar","Sophos","VIPRE"]
observed_at
2026-11-02 09:33:51
checked_at
2026-11-04 23:35:02
fetched_at
2026-11-04 22:35:02
time_basis
as stored; legacy timezone not established

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 80

SHA-256 6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a09a6e-1b45-7358-8992-1b7defb07388

Final URL

https://www.qntezlhu.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://www.qntezlhu.shop/
    From
    http://www.qntezlhu.shop/
    Status
    307

IP address

43.172.114.23

Contacted IP addresses

  • 43.172.114.23

Autonomous systems (ASN)

  • 132203

Server countries

  • SG

Document hash

6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

TLS session and certificate

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

Domain age, days

22

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

Registered domain age, days

281

Certificate age, days

22

Certificate validity, days

89

Page requests

2

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a09a6e-1b45-7358-8992-1b7defb07388
Final url
https://www.qntezlhu.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://www.qntezlhu.shop/",
        "from": "http://www.qntezlhu.shop/",
        "status": 307
    }
]
Ip
43.172.114.23
Contacted IP addresses
[
    "43.172.114.23"
]
Asns
[
    "132203"
]
Countries
[
    "SG"
]
Document hash
6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d
Tls
{
    "san": [
        "www.qntezlhu.shop"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "www.qntezlhu.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-20T06:27:02Z",
    "valid_from": "2026-08-22T06:27:03Z"
}
Domain age days
22

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

Apex age days
281
Tls age days
22
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 80,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}

OTX

4 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

90f118ad-fe2b-4e27-82f9-6b767a10e26b

Final URL

https://www.tiktok.com/

HTTP response

200

Redirect type

off-domain

Navigation history

  • URL
    https://qntezlhu.shop/
    Status
    302
  • URL
    https://www.tiktok.com/
    Status
    200

DOM structure hash

6b08f8dbcabfacd15d5f347b2e666b595dc58ef90cdc6909711e078cbc91cc96

Document hash

768b8c9c0403030675511b30f25c9c071a7711b721b01d5c65faff47fd44f705

Domain risk categories

  • Video Streaming
  • Entertainment
  • Social Networks
  • Society & Lifestyle

Cloudflare Radar rank

Rank range
200

DNS records

  • Name
    v16-webapp-prime.us.tiktok.com
    Type
    CNAME
    Value
    v16-webapp-prime.us.tiktok.com.edgesuite.net
  • Name
    v16-webapp-prime.us.tiktok.com
    Type
    CNAME
    Value
    v16-webapp-prime.us.tiktok.com.edgesuite.net
  • Name
    v19-webapp-prime.us.tiktok.com
    Type
    CNAME
    Value
    us.bytedance.map.fastly.net
  • Name
    v19-webapp-prime.us.tiktok.com
    Type
    CNAME
    Value
    us.bytedance.map.fastly.net
  • Name
    webcast.us.tiktok.com
    Type
    CNAME
    Value
    webcast.us.tiktok.com.edgesuite.net
  • Name
    webcast.us.tiktok.com
    Type
    CNAME
    Value
    webcast.us.tiktok.com.edgesuite.net
  • Name
    www.tiktok.com
    Type
    CNAME
    Value
    www.tiktok.com.edgesuite.net
  • Name
    www.tiktok.com
    Type
    CNAME
    Value
    www.tiktok.com.edgesuite.net

DNSSEC valid

No

IP address

127.0.1.7

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

Registration record

Registrar
Gandi SAS
Registered
Updated
Expires
Nameservers
  • a1-97.akam.net
  • a12-66.akam.net
  • a13-67.akam.net
  • a18-64.akam.net
  • a6-65.akam.net
  • a9-66.akam.net
Original source fields · JSON
Uuid
90f118ad-fe2b-4e27-82f9-6b767a10e26b
Final url
https://www.tiktok.com/
Status
200
Redirected
off-domain
History
[
    {
        "url": "https://qntezlhu.shop/",
        "status": 302
    },
    {
        "url": "https://www.tiktok.com/",
        "status": 200
    }
]
DOM structure hash
6b08f8dbcabfacd15d5f347b2e666b595dc58ef90cdc6909711e078cbc91cc96
Document hash
768b8c9c0403030675511b30f25c9c071a7711b721b01d5c65faff47fd44f705
Domain risks
[
    "Video Streaming",
    "Entertainment",
    "Social Networks",
    "Society & Lifestyle"
]
Radar rank
{
    "bucket": "200"
}
DNS records
[
    {
        "name": "v16-webapp-prime.us.tiktok.com",
        "type": "CNAME",
        "value": "v16-webapp-prime.us.tiktok.com.edgesuite.net"
    },
    {
        "name": "v16-webapp-prime.us.tiktok.com",
        "type": "CNAME",
        "value": "v16-webapp-prime.us.tiktok.com.edgesuite.net"
    },
    {
        "name": "v19-webapp-prime.us.tiktok.com",
        "type": "CNAME",
        "value": "us.bytedance.map.fastly.net"
    },
    {
        "name": "v19-webapp-prime.us.tiktok.com",
        "type": "CNAME",
        "value": "us.bytedance.map.fastly.net"
    },
    {
        "name": "webcast.us.tiktok.com",
        "type": "CNAME",
        "value": "webcast.us.tiktok.com.edgesuite.net"
    },
    {
        "name": "webcast.us.tiktok.com",
        "type": "CNAME",
        "value": "webcast.us.tiktok.com.edgesuite.net"
    },
    {
        "name": "www.tiktok.com",
        "type": "CNAME",
        "value": "www.tiktok.com.edgesuite.net"
    },
    {
        "name": "www.tiktok.com",
        "type": "CNAME",
        "value": "www.tiktok.com.edgesuite.net"
    }
]
Dnssec valid
false
Ip
127.0.1.7

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

Registration record
{
    "registrar": "Gandi SAS",
    "created": "1996-07-21T04:00:00Z",
    "updated": "2026-06-19T01:02:04Z",
    "expires": "2027-07-20T04:00:00Z",
    "nameservers": [
        "a1-97.akam.net",
        "a12-66.akam.net",
        "a13-67.akam.net",
        "a18-64.akam.net",
        "a6-65.akam.net",
        "a9-66.akam.net"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
qntezlhu.shop: Recorded redirect to www.tiktok.com video feed
ai_description
PhishDestroy records a redirect from qntezlhu.shop to www.tiktok.com, where the destination page shows a TikTok video feed with navigation and a login option.
ai_summary
On 2026-11-04, qntezlhu.shop redirected to www.tiktok.com. The destination page displays the TikTok interface with a dark theme, showing a left sidebar with navigation items such as For You, Shop, Explore, Following, Short dramas, LIVE, Upload, Profile, and More, along with a Log in button and a search field at the top. A central overlay panel with a Skip option and a loading spinner appears over the video area, and a bottom-right notice reads that TikTok Shop is now available on web. The stored VirusTotal domain result reports 12 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-04 23:39:29
revision
0147c712ac56f8fcf689296d2473e269875ecfc593ebc7a7c0399800483ed1eb
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

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

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
3
Archived days
4
Snapshots per day
0.13
Average page size, bytes
74851

Page title and metadata

Page title
500 Internal Server Error
Indexing directives
noindex, nofollow

Trackers

Requests
80
Observed services
  • Name
    Google Translate
    Company
    Google
    Country
    US
    Category
    Customer Interaction
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    5

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
274
TLS
160
Waiting
176
Connection
157
Download
1
Response time, ms
768

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

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

DNS servers

Nameservers
  • IP address
    61.172.183.77
    Host
    ns3.363.hk
  • IP address
    211.149.230.100
    Host
    ns4.363.hk
  • IP address
    118.123.249.114
    Host
    ns1.363.hk
  • IP address
    61.172.183.73
    Host
    ns2.363.hk
DNS zone
qntezlhu.shop

Cookies

Cookies
  • Name
    _fbp
  • Name
    _bazchg_vid
  • Name
    _bazchg_cvid
  • Name
    _bazchg_vs
  • Name
    utm_source
  • Name
    utm_medium
  • Name
    order_utm_history
  • Name
    landing_page
  • Name
    _bazchg_ka
  • Name
    first_http_referer
  • Name
    first_visit_time
  • Name
    currency_code
    Session cookie
    Yes
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    _BBZHBHI_ua
    Secure
    Yes
    SameSite
    None
  • Name
    _BBZHBHI_pu
    Secure
    Yes
    SameSite
    None
  • Name
    _BBZHBHI_tz
    Secure
    Yes
    SameSite
    None
  • Name
    _BBZHBHI_ss
    Secure
    Yes
    SameSite
    None
  • Name
    _BBZHBHI_lang
    Secure
    Yes
    SameSite
    None
  • Name
    _BBZHBHI_vs
    Secure
    Yes
    SameSite
    None
  • Name
    _BBZHBHI_dt
    Secure
    Yes
    SameSite
    None

Location

IP address
43.172.114.23
ASN
132203
Organization
Shenzhen Tencent Computer Systems Company Limited
City
San Jose
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
qntezlhu.shop

DNS records

A
  • 43.172.114.23
NS
  • ns2.363.hk
  • ns4.363.hk
  • ns1.363.hk
  • ns3.363.hk
SOA
Primary nameserver
ns1.363.hk
Hostmaster
dnsconct.363.hk
Serial
2026081305
Refresh, seconds
3600
Retry, seconds
300
Expiry, seconds
1209600
Minimum TTL, seconds
3600

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

Redirects

Redirect chain
  • https://qntezlhu.shop

Subdomains

Count
1
Subdomains
  • www.qntezlhu.shop

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-04T20:17:08Z",
    "first": "2026-10-13T12:04:01Z",
    "changes": 3,
    "days_archived": 4,
    "scans_per_day": 0.13,
    "avg_page_bytes": 74851
}
Page title and metadata
{
    "title": "500 Internal Server Error",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 80,
    "trackers": [
        {
            "name": "Google Translate",
            "company": "Google",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 5
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 274,
        "tls": 160,
        "wait": 176,
        "connect": 157,
        "download": 1
    },
    "response_ms": 768
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 219,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "61.172.183.77",
            "host": "ns3.363.hk"
        },
        {
            "ip": "211.149.230.100",
            "host": "ns4.363.hk"
        },
        {
            "ip": "118.123.249.114",
            "host": "ns1.363.hk"
        },
        {
            "ip": "61.172.183.73",
            "host": "ns2.363.hk"
        }
    ],
    "zone": "qntezlhu.shop"
}
Cookies
{
    "cookies": [
        {
            "name": "_fbp"
        },
        {
            "name": "_bazchg_vid"
        },
        {
            "name": "_bazchg_cvid"
        },
        {
            "name": "_bazchg_vs"
        },
        {
            "name": "utm_source"
        },
        {
            "name": "utm_medium"
        },
        {
            "name": "order_utm_history"
        },
        {
            "name": "landing_page"
        },
        {
            "name": "_bazchg_ka"
        },
        {
            "name": "first_http_referer"
        },
        {
            "name": "first_visit_time"
        },
        {
            "name": "currency_code",
            "session": true
        },
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "_BBZHBHI_ua",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBZHBHI_pu",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBZHBHI_tz",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBZHBHI_ss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBZHBHI_lang",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBZHBHI_vs",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBZHBHI_dt",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "43.172.114.23",
    "asn": "132203",
    "org": "Shenzhen Tencent Computer Systems Company Limited",
    "city": "San Jose",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "qntezlhu.shop"
}
DNS records
{
    "A": [
        "43.172.114.23"
    ],
    "NS": [
        "ns2.363.hk",
        "ns4.363.hk",
        "ns1.363.hk",
        "ns3.363.hk"
    ],
    "SOA": "{\"nsname\": \"ns1.363.hk\", \"hostmaster\": \"dnsconct.363.hk\", \"serial\": 2026081305, \"refresh\": 3600, \"retry\": 300, \"expire\": 1209600, \"minttl\": 3600}"
}
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.172.114.23",
    "family": 4
}
Redirects
{
    "chain": [
        "https://qntezlhu.shop"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.qntezlhu.shop"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about qntezlhu.shop

Is qntezlhu.shop legit?

PhishDestroy rates qntezlhu.shop as critical risk (96/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 12/92 engines flagged. malicious: 10. suspicious: 2. Analysis time (as stored): 2026-11-02T09:33:51Z. Retrieved (as stored): 2026-11-04T22:34:57Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is qntezlhu.shop safe to connect a wallet?

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

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

Explore

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

Checked, no match

Last checked

Stored Capture · 4 captures

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: 6a03e775d32c3e6f450f3c1a63b53c55e8aeeec9e3bb60a911b78501485b1d81 SHA-256 of the prepared copy given to the model: fd176ea51b21f6067c5fc7376f7a4cbc7aa382b3b56dde70d267a95225ef3c31
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://www.tiktok.com/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)
Observed page title
TikTok - Make Your Day
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 15 days

Domain details

Domain
IP Reputation United States43.172.114.23 abuse score 0/100 0 reports checked Nov 5, 2026
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar West263 International
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for qntezlhu.shop →
RegistrationCreated Dec 6, 2025 (333d) — Expires Dec 6, 2026
HTTP Status302 Found (Temporary)
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
DOM Analysisanalyzed Nov 4, 2026score 0/100
Submitted URLhttp://qntezlhu.shop/
Favicon Hash
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
United States43.172.114.23
Network ASN
AS132203
Organization
Shenzhen Tencent Computer Systems Company Limited
Observed location
United StatesSan Jose, US
Server header
nginx

Nameservers 6

  • a1-97.akam.net
  • a12-66.akam.net
  • a13-67.akam.net
  • a18-64.akam.net
  • a6-65.akam.net
  • a9-66.akam.net

SOA

  • nsname: ns1.363.hk
  • hostmaster: dnsconct.363.hk
  • serial: 2026081305
  • refresh: 3600
  • retry: 300
  • expire: 1209600
  • minttl: 3600

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-08-22 06:27:03
Valid until
2026-11-20 06:27:02
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6080a6214ca96417f91cbf9539a7710019df890c291add9c9b5453e1e74128bb
Certificate names · 1 SAN
  • qntezlhu.shop

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

viewdns.info · 43.172.114.23rapiddns.io
Recorded subdomains1

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

  • www.qntezlhu.shopDomain record
Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
DNS8
VIPRE
G-Data
Lionic
Sophos
CyRadar
Netcraft
SOCRadar
Gridinsoft
BitDefender
alphaMountain.ai
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of qntezlhu.shop · checked Nov 4, 2026

37
Poor
Performance
FCP
2.62 s
First Contentful Paint
LCP
17.44 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1601 ms
Total Blocking Time
SI
8.65 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://qntezlhu.shop/
Final URL: https://www.tiktok.com/
TikTok - Make Your Day
Response
HTTP 200
HTML body
422.3 KB
Compressed
91.5 KB
Links
0 internal · 0 external
Detected technologies
reactnginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
X-Powered-By: Goofy Node
Content-Encoding: gzip
Cache-Control: max-age=0, no-cache, no-store
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 36
Access-Control-Allow-Credentials
true
Access-Control-Expose-Headers
x-tt-traceflag,x-tt-logid
Cache-Control
max-age=0, no-cache, no-store
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
report-uri https://mon16-normal-useast5.tiktokv.us/monitor_browser/collect/batch/security/?bid=tiktok_pns&ev_type=csp&p=oAwsdSRvQQk4fDXvkPF5PR&v=4&s=392&b=oab; report-to csp-endpoint; upgrade-insecure-requests; default-src 'self' 'unsafe-eval' 'unsafe-inline' blob: bytedance: data: wss://*.tiktok.com wss://*.tiktokv.co
Content-Type
text/html; charset=utf-8
Date
Wed, 04 Nov 2026 20:52:16 GMT
Expires
Wed, 04 Nov 2026 20:52:16 GMT
Feature-Policy
microphone 'none'; geolocation 'none'
Pragma
no-cache
Referrer-Policy
strict-origin-when-cross-origin
reporting-endpoints
csp-endpoint="https://mon16-normal-useast5.tiktokv.us/monitor_browser/collect/batch/security/?bid=tiktok_pns&ev_type=csp&p=oAwsdSRvQQk4fDXvkPF5PR&v=4&s=392&b=oab"
Server
nginx
Server-Timing
cdn-cache; desc=MISS, edge; dur=26, origin; dur=249
Strict-Transport-Security
max-age=31536000; includeSubdomains
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Akamai-Request-ID
2086c219.76cc655
X-Bytefaas-Execution-Duration
239.52
X-Bytefaas-Request-Id
2026110420521601716DBA17E9181F306F
X-Cache
TCP_MISS from a23-202-158-7.deploy.akamaitechnologies.com (AkamaiGHost/22.7.0-c18a5259117e1d1b2cb0ace70ccfa9bb) (-)
X-Cache-Remote
TCP_MISS from a23-33-84-167.deploy.akamaitechnologies.com (AkamaiGHost/22.7.0-c18a5259117e1d1b2cb0ace70ccfa9bb) (-)
X-Content-Type-Options
nosniff
X-Download-Options
noopen
X-Frame-Options
SAMEORIGIN
X-Gw-Dst-Psm
serverless.tiktok.desktop
X-Origin-Response-Time
250,23.33.84.167
X-Parent-Response-Time
274,23.202.158.7
X-Powered-By
Goofy Node
X-Pumbaa-Web-Avail
1
X-Tt-Logid
2026110420521601716DBA17E9181F306F
x-tt-trace-host
019012c03ad17e9bdf0bb33c24277e228c1b00f8fb7ac5fb457f1f8de7bfcd57dfb846aaea2a8358ec8b5035d135d970e207f2ece33c8c4579e87077e35a3a09192f5178e5209a3b8e20926095dab63380ea2f2bd3ea0dbcfff7cc26bf5bb57f2acf57b1a65c471289cddea1e9cd090592
x-tt-trace-id
00-26110420521601716DBA17E9181F306F-786F279341F94905-00
x-tt-trace-tag
id=16;cdn-cache=miss;type=dyn
X-XSS-Protection
1; mode=block

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

Archived

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

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

Open this scan on URLScan 01a09a6e-1b45-7358-8992-1b7defb07388 ↗

Separate monitor HTTP observation

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

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-02 10:28:12
All retained availability observations1

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
    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-11-04 23:35:34.226128
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 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
    qntezlhu.shop detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Automated brand label: TikTok · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 80
  • 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: 12/92
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: TikTok
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Added to PhishDestroy

    qntezlhu.shop

    View source
  3. VirusTotal

    12/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 80

    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.

qntezlhu.shop

Evidence & External Reports

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

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including qntezlhu.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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

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

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

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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