Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 21. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
updateserv-owa.vercel.app favicon

updateserv-owa.vercel.app

In short

updateserv-owa.vercel.app is an Outlook impersonation page detected by PhishDestroy on 2026-10-22. Risk: critical (100/100). Registrar: Vercel. Status: Last known active. Hosting: Amazon.com, Inc. VirusTotal: 21/92 engines flag it. Do not enter credentials or connect a wallet.

“Outlook”

Review the evidence
Registrar
Vercel
Resolved IP
64.29.17.195
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 21/92 Automated brand label: Outlook Scam type: Impersonation
VirusTotal
21 / 92
engine detections ·
OTX
0
community references
Cloudflare Radar
—
Not recorded
Page captures
10
open gallery
Domain age
—
Not recorded
Reports sent
—
No sent record
Oct 22, 2026 CDN
X Telegram API
Source evidenceVirusTotal 21 / 92 7 sources

VirusTotal

21 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
21
Suspicious
0
Undetected
27

Vendor labels

ESET
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
URLQuery
malicious
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
MalwareURL
phishing
SafeToOpen
phishing
BitDefender
phishing
Criminal IP
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.67
  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.67

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": 44,
    "malicious": 21,
    "suspicious": 0,
    "undetected": 27
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "SafeToOpen": "phishing",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
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-08-15T05:55:06Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.67"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.67"
    }
]
Dns at
2026-10-20T14:40:05Z
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 source record · 21 malicious + 0 suspicious / 92 · 2026-10-20 14:35:44 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-20T14:35:44Z
fetched_at
2026-10-22T19:11:47Z
stats
{"timeout":0,"harmless":44,"malicious":21,"suspicious":0,"undetected":27}

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a164fe-3f3e-741d-9d17-3ddf14687984

Final URL

https://updateserv-owa.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://updateserv-owa.vercel.app/
    From
    http://updateserv-owa.vercel.app/
    Status
    307

IP address

64.29.17.131

Contacted IP addresses

  • 64.29.17.131

Autonomous systems (ASN)

  • 16509

Server countries

  • US

Document hash

73cc7ef56a56593ddf8d159c27035304b946f5c608a4fba935e696a326784a35

JavaScript globals

  • initLogon
  • redir
  • shw
  • hd
  • clkSecExp
  • kdSecExp
  • clkSec
  • clkBsc
  • checkSubmit
  • clkLgn
  • clkRtry
  • clkReLgn
  • gbid
  • IsOwaPremiumBrowser
  • hres
  • LogoffMime
  • addPerfMarker
  • a_fRC
  • g_fFcs
  • a_fLOff
  • a_fCAC
  • a_fEnbSMm
  • IsMimeCtlInst
  • RndMimeCtl
  • RndMimeCtlHlpr
  • mainLogonDiv
  • showPlaceholderText
  • mainLogonDivClassName
  • setPlaceholderText
  • showPasswordClick

Cookies

  • cookieTest

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

68

Registered domain age, days

68

Certificate age, days

53

Certificate validity, days

89

Page requests

8

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • microsoft
  • owa
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Microsoft
  • Outlook Web Access
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
01a164fe-3f3e-741d-9d17-3ddf14687984
Final url
https://updateserv-owa.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://updateserv-owa.vercel.app/",
        "from": "http://updateserv-owa.vercel.app/",
        "status": 307
    }
]
Ip
64.29.17.131
Contacted IP addresses
[
    "64.29.17.131"
]
Asns
[
    "16509"
]
Countries
[
    "US"
]
Document hash
73cc7ef56a56593ddf8d159c27035304b946f5c608a4fba935e696a326784a35
Globals
[
    "initLogon",
    "redir",
    "shw",
    "hd",
    "clkSecExp",
    "kdSecExp",
    "clkSec",
    "clkBsc",
    "checkSubmit",
    "clkLgn",
    "clkRtry",
    "clkReLgn",
    "gbid",
    "IsOwaPremiumBrowser",
    "hres",
    "LogoffMime",
    "addPerfMarker",
    "a_fRC",
    "g_fFcs",
    "a_fLOff",
    "a_fCAC",
    "a_fEnbSMm",
    "IsMimeCtlInst",
    "RndMimeCtl",
    "RndMimeCtlHlpr",
    "mainLogonDiv",
    "showPlaceholderText",
    "mainLogonDivClassName",
    "setPlaceholderText",
    "showPasswordClick"
]
Cookies
[
    "cookieTest"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Domain age days
68
Apex age days
68
Tls age days
53
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "microsoft",
            "owa"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Microsoft",
            "Outlook Web Access"
        ],
        "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 · 2026-10-23 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a164fe-3f3e-741d-9d17-3ddf14687984
score
100
malicious
true
result_at
2026-10-23T03:30:51Z
enriched_at
2026-10-24T08:17:26Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:51","urlscan_enriched_at":"2026-10-24 10:17:26"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

68 / 100 · heuristic score · 1 brand references · 1 classifications

Open report
Separate monitor score · 25 / 100 · 2026-10-22T22:20:18Z

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
25
analyzed_at
2026-10-22T22:20:18Z
source_timestamp
2026-10-23 00:20:18
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

SPF lookups
0

CAA records

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

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
Outlook

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
31
TLS
10
Waiting
13
Connection
6
Download
8
Response time, ms
68

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
58907
CO₂, grams
0.0022
Cleaner than, %
33

DNS servers

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

Cookies

Cookies
  • Name
    cookieTest
    Session cookie
    Yes

Location

IP address
216.198.79.131
ASN
16509
Organization
Amazon.com, Inc.
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
216.198.79.131
IP version
4

Redirects

Redirect chain
  • https://updateserv-owa.vercel.app

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": [
        "pki.goog",
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "Outlook"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 31,
        "tls": 10,
        "wait": 13,
        "connect": 6,
        "download": 8
    },
    "response_ms": 68
}
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": 58907,
    "co2_grams": 0.0022,
    "cleaner_than": 33
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Cookies
{
    "cookies": [
        {
            "name": "cookieTest",
            "session": true
        }
    ]
}
Location
{
    "ip": "216.198.79.131",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "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": "216.198.79.131",
    "family": 4
}
Redirects
{
    "chain": [
        "https://updateserv-owa.vercel.app"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}

Questions about updateserv-owa.vercel.app

Is updateserv-owa.vercel.app legit?

No. PhishDestroy classifies updateserv-owa.vercel.app as an Outlook impersonation page (risk: critical, 100/100); it was first detected on 2026-10-22. VirusTotal: 21/92 engines flag it. Treat the site as unsafe.

Is updateserv-owa.vercel.app safe to connect a wallet?

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

What should I do if I used updateserv-owa.vercel.app?

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

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 10
Open capture Wayback Download
All capture links and hashes (10)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Microsoftbrand: Owa report ↗
IP Context 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 Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 23, 2026score 68/1001 brand signal
Submitted URLhttp://updateserv-owa.vercel.app/
Observed page title
Outlook
Automated brand references
Outlook
TLS Certificate
Issued by Google Trust Services / WR1 · stored validity ends in 32 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.29.17.195
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Walnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
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.195rapiddns.io

Latest Classified Outcome 2026-10-25 23:01: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: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-25 23:01:35 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 02:54:30 UTC last content: 2026-10-25 02:54:30 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

21 / 92 security vendors flagged this domain
View on VT
Last analyzed
Criminal IP
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
SafeToOpen
SOCRadar
Sophos
URLQuery
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
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.

Stored observation history2

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

    Unknown→live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations13

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_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-26 00:01:35.000000
    Evidence SHA-256
    e9bb5fff0b42ea75adf2dad7f53fd551fb37ae7c62653777ba668858442a110e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:35
    Evidence reason
    alive_content
  2. 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-25 12:01:42.000000
    Evidence SHA-256
    8009dd3eb0cf52740944e11c7c6d977106b47781960a74983a28804721cdac3d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:01:42
    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-10-25 12:01:42.000000
    Evidence SHA-256
    8009dd3eb0cf52740944e11c7c6d977106b47781960a74983a28804721cdac3d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:01:42
    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
    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-25 03:54:30.000000
    Evidence SHA-256
    b45b6b61d631d9fa632e205d2483c3f6863ec654ec58ece370c1e1ceecf25c22
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:30
    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-10-25 03:54:30.000000
    Evidence SHA-256
    b45b6b61d631d9fa632e205d2483c3f6863ec654ec58ece370c1e1ceecf25c22
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:30
    Evidence reason
    alive_content
  6. 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-24 12:00:35.000000
    Evidence SHA-256
    77fd1ac5557401ce310f4dd4ef0f2fb7978aca29c76dac2128ff1628ba44ed3e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:35
    Evidence reason
    alive_content
  7. 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-24 12:00:35.000000
    Evidence SHA-256
    77fd1ac5557401ce310f4dd4ef0f2fb7978aca29c76dac2128ff1628ba44ed3e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:35
    Evidence reason
    alive_content
  8. 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-24 00:00:42.000000
    Evidence SHA-256
    080fb785995fe935f787c91c5f41037e7609462302c71e363fb06279fc998ca7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:42
    Evidence reason
    alive_content
  9. 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-24 00:00:42.000000
    Evidence SHA-256
    080fb785995fe935f787c91c5f41037e7609462302c71e363fb06279fc998ca7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:42
    Evidence reason
    alive_content
  10. 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-23 12:00:33.000000
    Evidence SHA-256
    4f87125a115c46adf3df61f023107379996679f3297d93fd4a30520f192f1646
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:33
    Evidence reason
    alive_content
  11. 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-23 12:00:33.000000
    Evidence SHA-256
    4f87125a115c46adf3df61f023107379996679f3297d93fd4a30520f192f1646
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:33
    Evidence reason
    alive_content
  12. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-22 21:03:42.000000
    Evidence SHA-256
    87bcec952873f286a52e01c29027bc3d40685a821eb90f042a942cecf60f0921
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 21:03:42
    Evidence reason
  13. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-22 21:03:42.000000
    Evidence SHA-256
    87bcec952873f286a52e01c29027bc3d40685a821eb90f042a942cecf60f0921
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 21:03:42
    Evidence reason

Recorded activity

4 entries
  1. VirusTotal

    21/92 engine detections

    View source
  2. Added to PhishDestroy

    updateserv-owa.vercel.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

updateserv-owa.vercel.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 21 det. ChainPatrol URLQuery 5 det. SSL Labs Stored certificate dates valid 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.

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 →.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

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

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/updateserv-owa.vercel.app"
  title="PhishDestroy threat report for updateserv-owa.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>