The domain sushi.com-vivid-web.bond returned HTTP status 502 in an HTTP check dated 2026-10-01. Separately, the domain was first observed on 2026-09-13, and a PhishDestroy internal listing is recorded as true.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502. The first observation date for the domain is 2026-09-13. A VirusTotal check on 2026-09-21 recorded 5 detections across 89 scanners. The PhishDestroy internal listing is recorded as true. The IP address 194.110.247.29 is associated with the domain, with IP country MD and IP organization AS200019 ALEXHOST SRL.
Interpretation
The recorded HTTP 502 response describes only the response captured at that check, not all content that may be served by the domain. The PhishDestroy internal listing and the VirusTotal detection count are separate source records with different dates, so they should be read as distinct observations rather than combined into a single conclusion. The gap between the first observation and the HTTP check shows the domain was recorded before the response was captured, but the records do not establish what changed in between.
Recommended Actions
Preserve the PhishDestroy internal listing record and the VirusTotal check record for sushi.com-vivid-web.bond, and compare them against any later observations of the same domain. Retain the HTTP check record alongside the first observation date so future reviews can compare the recorded response with the earlier observation. Treat the recorded HTTP status as a dated response only, and avoid relying on it as a statement about current availability.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sushi.com-vivid-web.bond', port=80): Max retries exceeded with url: / (Caused by NewConnec
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)com-vivid-web.bond · Created Sep 12, 2026 (29d · Very New!)
Time to First Unavailability7 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 13, 2026
SHORTDOT ZONE · PUBLIC EVIDENCE.bond
ShortDot zone evidence
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
For the registrable domain com-vivid-web.bond behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
194.110.247.29
Network ASN
AS200019
Organization
ALEXHOST SRL
Observed location
Chisinau, MD
Server header
nginx
Nameservers 1
ns3.openprovider.eu
Location describes the IP network.
TLS certificate
Issuer
YE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:29:45 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-13 05:28:11 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-13 05:28:11 UTC → 2026-09-30 16:14:55 UTC · 418.78hmidpoint estimate ≈ 2026-09-21 22:51:33 UTC · precision low · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Fortinet
LevelBlue
SOCRadar
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-20 19:52:28 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
Domain Status Transition2026-09-19 22:00:24 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-19 18:21:08 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
sushi.com-vivid-web.bond detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 20, 2026
Time to First Unavailability
161 hours elapsed from detection to the first unavailable observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
We are writing to report a phishing website that has been built to impersonate the SushiSwap exchange and to harvest visitors' cryptocurrency wallets. The domain sushi[.]com-vivid-web[.]bond was registered today, 12 September 2026, and its host name was chosen so that the browser
1 report filed for sushi.com-vivid-web.bond (1 written by a person) · category: Phishing · source checked
“We are writing to report a phishing website that has been built to impersonate the SushiSwap exchange and to harvest visitors' cryptocurrency wallets. The domain sushi[.]com-vivid-web[.]bond was registered today, 12 September 2026, and its host name was chosen so that the browser's address bar reads "sushi.com" first, matching the exchange's real address, with the rest of the name trailing behind where it is easily overlooked.
The domain does not answer an ordinary visitor. A request made strai”
— reported by Anonymous on Sep 12, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
3 evidence signal groups linked0 reports recordedContent unavailable
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.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · sushi.com-vivid-web.bond
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(NL)
