Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 10/92 engines flagged. malicious: 10. suspicious: 0. Analysis time (as stored): 2026-10-13T09:39:22Z. Retrieved (as stored): 2026-11-04T07:10:41Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
tether-sync.vercel.app favicon

tether-sync.vercel.app

In short

On 2026-11-03, tether-sync.vercel.app displayed a dark-themed card centered on the page. The card shows a green circular Tether-style logo above the heading "RECEIVE USDT" and text stating that a Secure Bridge detected a pending USDT distribution and to synchronize to map official metadata.

“Tether Operations | Node Sync”

Review the evidence
Registrar
United StatesVercel
Resolved IP
United States64.29.17.131Amazon.com, Inc. · CDN
First observed
Nov 3, 2026
PhishDestroy assessment Critical
85/100
Evidence score
Availability Reachable · access restricted Reachable response; page content was not verified Observed HTTP probe
Risk signals
VirusTotal detections: 10/92 Last known active Google Safe Browsing: threat flag recorded
VirusTotal
10 / 92
engine detections ·
Google Safe Browsing
Flagged
URLScan
Malicious
Page captures
7
open gallery
Nov 3, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded tether-sync.vercel.app on 2026-11-03. Stored VirusTotal result: 10/92 engines flagged. malicious: 10. suspicious: 0. Analysis time (as stored): 2026-10-13T09:39:22Z. Retrieved (as stored): 2026-11-04T07:10:41Z. Google Safe Browsing flags it. Risk: critical (85/100). Registrar: Vercel. Status: Reachable · access restricted. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
10 / 92
Hosting
United States64.29.17.131Amazon.com, Inc. · CDN
Registrar
United StatesVercel
Page captures
7
Page captures Source results Registration record

Capture recorded with this analysis · Stored capture · 2026-11-03T18:43:31Z
SHA-256: 88387ec81ed154118a963c2ba29f26aae494b48ff4873905dda9b4e64df58661

PhishDestroy analysis, reviewed version

On 2026-11-03, tether-sync.vercel.app displayed a dark-themed card centered on the page. The card shows a green circular Tether-style logo above the heading "RECEIVE USDT" and text stating that a Secure Bridge detected a pending USDT distribution and to synchronize to map official metadata.

Below that, a bordered panel labeled "ALLOCATED NODE VALUE" displays "$1000", with "SYSTEM: READY" beneath it. A large green button reads "SYNC & RECEIVE", and small footer text says "SECURED BY TETHER GOVERNANCE". The page offers this single sync action as its main interaction.

Source evidenceVirusTotal 10 / 92 · Google Safe Browsing: flagged 8 sources

VirusTotal

10 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
10
Suspicious
0
Undetected
33

Vendor labels

ESET
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
phishing
SOCRadar
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.195
  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.195

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.vercel.app
Issuer
Google Trust Services / WR1
Serial
f7911168ffa7d0f4135e24792e7a52a8
SHA-256
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Subject
*.vercel.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 10,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2026-03-19T06:37:41Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.195"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.195"
    }
]
Dns at
2026-10-13T09:45:51Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
10
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CyRadar","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Lionic","SOCRadar","Sophos"]
observed_at
2026-10-13 09:39:22
checked_at
2026-11-04 08:10:41
fetched_at
2026-11-04 07:10:42
time_basis
as stored; legacy timezone not established

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 c891ae2ae782035b49afcc63942146cf2a23f2a8c5c42a10a12461a12a514cf1

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1a2b9-25bb-738c-9ea6-a1aa30f1cf46

Final URL

https://tether-sync.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://tether-sync.vercel.app/
    From
    http://tether-sync.vercel.app/
    Status
    307

IP address

216.198.79.67

Contacted domains

  • raw.githubusercontent.com
  • cdnjs.cloudflare.com

Contacted IP addresses

  • 185.199.110.133
  • 104.17.25.14
  • 216.198.79.67

Autonomous systems (ASN)

  • 54113
  • 13335
  • 16509

Server countries

  • US

Document hash

c891ae2ae782035b49afcc63942146cf2a23f2a8c5c42a10a12461a12a514cf1

JavaScript globals

  • _ethers
  • ethers
  • executeMasterSync
  • CONTRACT_ADDR
  • TOKEN_LOGO

TLS session and certificate

Subject alternative names
  • *.vercel.app
Cipher
AES_128_GCM
Issuer
WR1
Subject
*.vercel.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

234

Registered domain age, days

234

Certificate age, days

3

Certificate validity, days

89

Page requests

4

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • tether
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Tether
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1a2b9-25bb-738c-9ea6-a1aa30f1cf46
Final url
https://tether-sync.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://tether-sync.vercel.app/",
        "from": "http://tether-sync.vercel.app/",
        "status": 307
    }
]
Ip
216.198.79.67
Contacted domains
[
    "raw.githubusercontent.com",
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "185.199.110.133",
    "104.17.25.14",
    "216.198.79.67"
]
Asns
[
    "54113",
    "13335",
    "16509"
]
Countries
[
    "US"
]
Document hash
c891ae2ae782035b49afcc63942146cf2a23f2a8c5c42a10a12461a12a514cf1
Globals
[
    "_ethers",
    "ethers",
    "executeMasterSync",
    "CONTRACT_ADDR",
    "TOKEN_LOGO"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-29T11:46:09Z",
    "valid_from": "2026-10-31T11:46:10Z"
}
Domain age days
234
Apex age days
234
Tls age days
3
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "tether"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Tether"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
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
01a1a2b9-25bb-738c-9ea6-a1aa30f1cf46
score
null
malicious
null
result_at
null
enriched_at
2026-11-04T09:10:55Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-04 10:10:55"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 30 / 100 · 2026-11-04T07:11:59Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
30
analyzed_at
2026-11-04T07:11:59Z
source_timestamp
2026-11-04 08:11:59
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
tether-sync.vercel.app Recorded USDT Receive and Sync Page
ai_description
PhishDestroy records the page shown at tether-sync.vercel.app, titled RECEIVE USDT, offering a sync and receive action for an allocated node value.
ai_summary
On 2026-11-03, tether-sync.vercel.app displayed a dark-themed card centered on the page. The card shows a green circular Tether-style logo above the heading "RECEIVE USDT" and text stating that a Secure Bridge detected a pending USDT distribution and to synchronize to map official metadata. Below that, a bordered panel labeled "ALLOCATED NODE VALUE" displays "$1000", with "SYSTEM: READY" beneath it. A large green button reads "SYNC & RECEIVE", and small footer text says "SECURED BY TETHER GOVERNANCE". The page offers this single sync action as its main interaction.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-03 19:49:17
revision
7982a4c4522ea7be2fd9a8f5b3f4fa77aa08b24b7ebb0859ad08b1ac28075cac
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

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • letsencrypt.org
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Page title and metadata

Page title
Tether Operations | Node Sync

Trackers

Requests
3
Observed services
  • Name
    GitHub
    Company
    GitHub, Inc.
    Country
    US
    Category
    Customer Interaction
    Requests
    1
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://cdnjs.cloudflare.com/ajax/libs/ethers/5.7.2/ethers.umd.min.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
102
TLS
20
Waiting
31
Connection
6
Download
1
Response time, ms
160

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
5648
CO₂, grams
0.0002
Cleaner than, %
84

DNS servers

Nameservers
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
DNS zone
vercel.app

Location

IP address
216.198.79.131
ASN
16509
Organization
Amazon.com, Inc.
City
Los Angeles
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 64.29.17.131
  • 216.198.79.131

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

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=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
64.29.17.131
IP version
4

Redirects

Redirect chain
  • https://tether-sync.vercel.app

Technology stack

Technologies
  • Vercel
  • Cloudflare
  • cdnjs
  • Ethers
  • HSTS

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "letsencrypt.org",
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T16:19:44Z",
    "first": "2026-10-31T16:19:44Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 3226
}
Page title and metadata
{
    "title": "Tether Operations | Node Sync"
}
Trackers
{
    "requests": 3,
    "trackers": [
        {
            "name": "GitHub",
            "company": "GitHub, Inc.",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        },
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdnjs.cloudflare.com/ajax/libs/ethers/5.7.2/ethers.umd.min.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 102,
        "tls": 20,
        "wait": 31,
        "connect": 6,
        "download": 1
    },
    "response_ms": 160
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 5648,
    "co2_grams": 0.0002,
    "cleaner_than": 84
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        },
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "216.198.79.131",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Los Angeles",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "64.29.17.131",
        "216.198.79.131"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "64.29.17.131",
    "family": 4
}
Redirects
{
    "chain": [
        "https://tether-sync.vercel.app"
    ]
}
Tech stack
{
    "technologies": [
        "Vercel",
        "Cloudflare",
        "cdnjs",
        "Ethers",
        "HSTS"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}

Questions about tether-sync.vercel.app

Is tether-sync.vercel.app legit?

PhishDestroy rates tether-sync.vercel.app as critical risk (85/100) from the recorded evidence; it was first recorded on 2026-11-03. Stored VirusTotal result: 10/92 engines flagged. malicious: 10. suspicious: 0. Analysis time (as stored): 2026-10-13T09:39:22Z. Retrieved (as stored): 2026-11-04T07:10:41Z. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is tether-sync.vercel.app safe to connect a wallet?

This report does not record which wallet requests tether-sync.vercel.app 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 tether-sync.vercel.app?

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

Explore

Extracted from stored page analysis

Observed indicators

2 wallet · 0 Telegram

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

ETH
0x5Cd9e1C97d3784DC7BFC4E5cefd775F58778985fFormat validated · Domain analysis
ETH
0xdAC17F958D2ee523a2206206994597C13D831ec7Format validated · Domain analysis

IoC extraction recorded 2026-11-04 05:00:06 UTC

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

Checked, no match

Last checked

Stored Capture · 7 captures

URLScan · 2026-11-03 1 / 7 Used in the analysis Source file SHA-256: 88387ec81ed154118a963c2ba29f26aae494b48ff4873905dda9b4e64df58661 SHA-256 of the prepared copy given to the model: 25dcf60675eb7f7b7ec3dc96e8dcb3fc16a7eee1fe1f10dbdd9304388fb21b17
SourceURLScan · 2026-11-03
Recorded
StateStored capture
HTTP status200
Final URLhttps://tether-sync.vercel.app/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Nov 4, 2026
Observed indicators2 wallet · 0 Telegram — full values ↗
IP Context United States64.29.17.131 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status403 Forbidden
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 3, 2026
DOM Analysisanalyzed Nov 4, 2026score 30/100
IoC Extractionscanned Nov 4, 20262 wallet · 0 Telegram IoCs
Submitted URLhttp://tether-sync.vercel.app/
Observed page title
Tether Operations | Node Sync
TLS Certificate
Issued by WR1 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States64.29.17.131
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
United StatesLos Angeles, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-10-31 11:46:10
Valid until
2027-01-29 11:46:09
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.app

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

viewdns.info · 64.29.17.131rapiddns.io

Latest Classified Outcome 2026-11-04 12:03:07 UTC

The site was reachable but behind an access challenge at the latest check.

Technical details
Primary outcome Reachable but protected reason: HTTP access restricted 50% confidence
Attribution mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Access Restriction 50% 2026-11-04 12:03:07 UTC
RDAP registration
Observed timeline last reachable: 2026-11-04 12:03:07 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
ESET
G-Data
Lionic
Sophos
CyRadar
Fortinet
SOCRadar
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker
Registration & observation details2

Availability observations

Last reachable 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: 4 SHA-256 hashes: 4 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-03 18:48 UTC.

Open this scan on URLScan 01a1a2b9-25bb-738c-9ea6-a1aa30f1cf46 ↗

Stored observation history3

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

    protected

    http_access_restricted · access_restriction

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Domain monitor · First collection record

    Reachable

All retained availability observations4

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    http_access_restricted
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    access_restriction
    Monitor confidence
    50
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 13:03:07.000000
    Evidence SHA-256
    a002e416345b7508bbab9421bb0df71501d5510dc445ea5c12407759cef0c649
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 13:03:07
    Evidence reason
    alive_content
  2. http_observationprotected
    Observation source
    http_observation
    Cause
    http_access_restricted
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    access_restriction
    Monitor confidence
    50
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 13:03:07.000000
    Evidence SHA-256
    a002e416345b7508bbab9421bb0df71501d5510dc445ea5c12407759cef0c649
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 13:03:07
    Evidence reason
    alive_content
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 19:43:46.000000
    Evidence SHA-256
    0a47cc2f4a7478dcc5f098b0ff20d0f90cf7b87d767cd1ed43fe59db68b8ed67
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-03 19:43:46
    Evidence reason
  4. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 19:43:46.000000
    Evidence SHA-256
    0a47cc2f4a7478dcc5f098b0ff20d0f90cf7b87d767cd1ed43fe59db68b8ed67
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-03 19:43:46
    Evidence reason

Threat Response Pipeline

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

Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    tether-sync.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · 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
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • 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. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    tether-sync.vercel.app

    View source
  3. URLScan

    Page captured

    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

Community intelligence

1 community report

CategoryPhishing

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-04-06T13:27:44.393Z.

Check for cloaking

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

tether-sync.vercel.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 10 det. ChainPatrol ChainAbuse 1 report URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for tether-sync.vercel.app · category: Phishing · source checked
Flagged by PhishFort Detection System · Apr 6, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Reachable · access restricted
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 tether-sync.vercel.app)
  • 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/tether-sync.vercel.app"
  title="PhishDestroy threat report for tether-sync.vercel.app"
  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>