Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 19. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
homivas.shop favicon

homivas.shop

In short

PhishDestroy stores a record for homivas.shop. Source observations are dated separately; missing checks do not establish safety.

“Black Friday sale”

Review the evidence
Registrar
United StatesSpaceship
Resolved IP
United States43.153.77.222Shenzhen Tencent Computer Systems Company Limited
Registered
Oct 7, 2026
First observed
Oct 28, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 19/92 Spamhaus DBL: phishing domain Young domain: 24 days old
VirusTotal
19 / 92
engine detections ·
OTX
4
community references
URLScan
Malicious
engine verdict · score 82
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
24 days
registered 2026-10-07 according to WHOIS
Reports sent
1
view timeline
OTX: 4 refs Oct 28, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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

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

Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-9667B3CFE0656B89488A
Current status
HTTP 200 at latest stored check

Questions about homivas.shop

Is homivas.shop legit?

PhishDestroy stores a record for homivas.shop. Source observations are dated separately; missing checks do not establish safety.

Is homivas.shop safe to connect a wallet?

This report does not record which wallet requests homivas.shop makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used homivas.shop?

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

Explore

Source evidenceVirusTotal 19 / 92 · OTX 4 references 8 sources

VirusTotal

19 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
42
Malicious
15
Suspicious
4
Undetected
31

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
spam
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.dnsip.com
  • TTL, seconds
    600
    Type
    A
    Value
    43.153.77.222
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.dnsip.com
  • TTL, seconds
    600
    Type
    SOA
    Responsible mailbox
    dnsadmin.dnsip.com
    Value
    ns1.dnsip.com

DNS records observed

JARM fingerprint

15d3fd16d29d29d00042d43d00000041ad16ead50175e1e575f5579aa6b5c8

Certificate

Subject alternative names
  • homivas.shop
Issuer
Let's Encrypt / YR2
Serial
584cc66098a88119a932b616a9444328fa9
SHA-256
13b5691922ee1af4b496680676cc9ea929238141a8151ccdb3efa66e492d0047
Subject
homivas.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 15,
    "suspicious": 4,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "spam",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
First seen
2026-10-07T09:10:35Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.dnsip.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "43.153.77.222"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.dnsip.com"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "dnsadmin.dnsip.com",
        "value": "ns1.dnsip.com"
    }
]
Dns at
2026-10-27T17:17:23Z
Jarm
15d3fd16d29d29d00042d43d00000041ad16ead50175e1e575f5579aa6b5c8
Certificate
{
    "san": [
        "homivas.shop"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "584cc66098a88119a932b616a9444328fa9",
    "sha256": "13b5691922ee1af4b496680676cc9ea929238141a8151ccdb3efa66e492d0047",
    "subject": "homivas.shop",
    "valid_to": "2027-01-05T08:01:54Z",
    "valid_from": "2026-10-07T08:01:55Z"
}
Separate source record · 15 malicious + 4 suspicious / 92 · 2026-10-27 17:11:42 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-27T17:11:42Z
fetched_at
2026-10-28T22:48:26Z
stats
{"timeout":0,"harmless":42,"malicious":15,"suspicious":4,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

513cba23-3236-46a0-a789-13ff62792ecf

Final URL

https://homivas.shop/

HTTP response

200

Navigation history

  • URL
    https://homivas.shop/
    Status
    200

DOM structure hash

8bae400e0e340f0d32f1f899dda0da029020a37042af05d7f05b6a8c87807a0b

Document hash

d1f3fd3511e8788dacf22c06146d7a77845787d9f1dd40f1bf420108d5d8ac25

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • Newly Seen Domains
  • Security Risks
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    homivas.shop
    Type
    A
    Value
    43.153.77.222

DNSSEC valid

No

IP address

127.0.1.42

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware
Original source fields · JSON
Uuid
513cba23-3236-46a0-a789-13ff62792ecf
Final url
https://homivas.shop/
Status
200
History
[
    {
        "url": "https://homivas.shop/",
        "status": 200
    }
]
DOM structure hash
8bae400e0e340f0d32f1f899dda0da029020a37042af05d7f05b6a8c87807a0b
Document hash
d1f3fd3511e8788dacf22c06146d7a77845787d9f1dd40f1bf420108d5d8ac25
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "Newly Seen Domains",
    "Security Risks",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "homivas.shop",
        "type": "A",
        "value": "43.153.77.222"
    }
]
Dnssec valid
false
Ip
127.0.1.42

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 82

SHA-256 931d2aedcbb3de14a7a28aa71ba6a83f7560b3f7c7afe43897788f6107fdf706

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a184a8-6734-723d-b4e8-e0996cd4fa2c

Final URL

https://homivas.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://homivas.shop/
    From
    http://homivas.shop/
    Status
    307

IP address

43.153.77.222

Contacted IP addresses

  • 43.153.77.222

Autonomous systems (ASN)

  • 132203

Server countries

  • US

Document hash

6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

TLS session and certificate

Subject alternative names
  • homivas.shop
Cipher
AES_128_GCM
Issuer
YR2
Subject
homivas.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

21

Registered domain age, days

21

Certificate age, days

21

Certificate validity, days

89

Page requests

2

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a184a8-6734-723d-b4e8-e0996cd4fa2c
Final url
https://homivas.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://homivas.shop/",
        "from": "http://homivas.shop/",
        "status": 307
    }
]
Ip
43.153.77.222
Contacted IP addresses
[
    "43.153.77.222"
]
Asns
[
    "132203"
]
Countries
[
    "US"
]
Document hash
6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d
Tls
{
    "san": [
        "homivas.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "homivas.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-05T08:01:54Z",
    "valid_from": "2026-10-07T08:01:55Z"
}
Domain age days
21
Apex age days
21
Tls age days
21
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 82,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}
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
01a11b6c-13e4-7379-87d7-8d281a3a09da
score
null
malicious
null
result_at
null
enriched_at
2026-10-29T09:15:38Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-29 10:15:38"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

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

Collected source details

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

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

Mail configuration

SPF lookups
0

CAA records

Domain
homivas.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.05
Average page size, bytes
62373

Page title and metadata

Page title
500 Internal Server Error
Indexing directives
noindex, nofollow

Trackers

Requests
22
Observed services
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
223
TLS
192
Waiting
308
Connection
157
Download
0
Response time, ms
880

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

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

DNS servers

Nameservers
  • IP address
    1.193.216.199
    Host
    ns1.dnsip.com
  • IP address
    211.99.99.33
    Host
    ns2.dnsip.com
DNS zone
homivas.shop

Cookies

Cookies
  • Name
    ip_auth_debug
  • Name
    _ahcccd_vid
  • Name
    _ahcccd_cvid
  • Name
    _ahcccd_vs
  • Name
    utm_source
  • Name
    utm_medium
  • Name
    order_utm_history
  • Name
    landing_page
  • Name
    _ahcccd_ka
  • Name
    first_http_referer
  • Name
    first_visit_time
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    _BBFZFZE_ua
    Secure
    Yes
    SameSite
    None
  • Name
    _BBFZFZE_pu
    Secure
    Yes
    SameSite
    None
  • Name
    _BBFZFZE_tz
    Secure
    Yes
    SameSite
    None
  • Name
    _BBFZFZE_ss
    Secure
    Yes
    SameSite
    None
  • Name
    _BBFZFZE_lang
    Secure
    Yes
    SameSite
    None
  • Name
    _BBFZFZE_vs
    Secure
    Yes
    SameSite
    None
  • Name
    _BBFZFZE_dt
    Secure
    Yes
    SameSite
    None

Location

IP address
43.153.77.222
ASN
132203
Organization
Shenzhen Tencent Computer Systems Company Limited
City
Santa Clara
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
homivas.shop

DNS records

A
  • 43.153.77.222
NS
  • ns1.dnsip.com
  • ns2.dnsip.com
SOA
Primary nameserver
ns1.dnsip.com
Hostmaster
dnsadmin.dnsip.com
Serial
1791358878
Refresh, seconds
3600
Retry, seconds
300
Expiry, seconds
1209600
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

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

IP lookup

IP address
43.153.77.222
IP version
4

Redirects

Redirect chain
  • https://homivas.shop

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "homivas.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-28T22:13:50Z",
    "first": "2026-10-07T10:19:39Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.05,
    "avg_page_bytes": 62373
}
Page title and metadata
{
    "title": "500 Internal Server Error",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 22,
    "trackers": [
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 223,
        "tls": 192,
        "wait": 308,
        "connect": 157,
        "download": 0
    },
    "response_ms": 880
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 219,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "1.193.216.199",
            "host": "ns1.dnsip.com"
        },
        {
            "ip": "211.99.99.33",
            "host": "ns2.dnsip.com"
        }
    ],
    "zone": "homivas.shop"
}
Cookies
{
    "cookies": [
        {
            "name": "ip_auth_debug"
        },
        {
            "name": "_ahcccd_vid"
        },
        {
            "name": "_ahcccd_cvid"
        },
        {
            "name": "_ahcccd_vs"
        },
        {
            "name": "utm_source"
        },
        {
            "name": "utm_medium"
        },
        {
            "name": "order_utm_history"
        },
        {
            "name": "landing_page"
        },
        {
            "name": "_ahcccd_ka"
        },
        {
            "name": "first_http_referer"
        },
        {
            "name": "first_visit_time"
        },
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "_BBFZFZE_ua",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBFZFZE_pu",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBFZFZE_tz",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBFZFZE_ss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBFZFZE_lang",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBFZFZE_vs",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BBFZFZE_dt",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "43.153.77.222",
    "asn": "132203",
    "org": "Shenzhen Tencent Computer Systems Company Limited",
    "city": "Santa Clara",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "homivas.shop"
}
DNS records
{
    "A": [
        "43.153.77.222"
    ],
    "NS": [
        "ns1.dnsip.com",
        "ns2.dnsip.com"
    ],
    "SOA": "{\"nsname\": \"ns1.dnsip.com\", \"hostmaster\": \"dnsadmin.dnsip.com\", \"serial\": 1791358878, \"refresh\": 3600, \"retry\": 300, \"expire\": 1209600, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "43.153.77.222",
    "family": 4
}
Redirects
{
    "chain": [
        "https://homivas.shop"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Security Risks Malware
View full Cloudflare Radar report
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded
StateStored capture
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)
Observed page title
Black Friday sale
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 65 days
homivas.shop: caution — Flagged by Spamhaus DBL, 19/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card homivas.shop: caution — Flagged by Spamhaus DBL, 19/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v d02a54fca746

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 82 report ↗
IP Reputation United States43.153.77.222 abuse score 0/100 0 reports checked Oct 29, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
Abuse contactabuse@tencent.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for homivas.shop →
Hosting abuse contact abuse@tencent.com Shenzhen Tencent Computer Systems Company Limited · AS132203
RegistrationCreated Oct 7, 2026 (24d · Very New!) — Expires Oct 7, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 28, 2026
DOM Analysisanalyzed Oct 28, 2026score 100/100
Submitted URLhttp://homivas.shop/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States43.153.77.222
Network ASN
AS132203
AS name
TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN
Organization
Shenzhen Tencent Computer Systems Company Limited
Observed location
United StatesSanta Clara, US
Server header
nginx

Nameservers 2

  • ns1.dnsip.com
  • ns2.dnsip.com

SOA

  • nsname: ns1.dnsip.com
  • hostmaster: dnsadmin.dnsip.com
  • serial: 1791358878
  • refresh: 3600
  • retry: 300
  • expire: 1209600
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-07 08:01:55
Valid until
2027-01-05 08:01:54
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint13b5691922ee1af4b496680676cc9ea929238141a8151ccdb3efa66e492d0047
Certificate names · 1 SAN
  • homivas.shop

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

viewdns.info · 43.153.77.222rapiddns.io

Latest Classified Outcome 2026-10-31 02:55:52 UTC

The site was serving its pages at the latest check.

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

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

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

VirusTotal Analysis

19 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 19 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of homivas.shop · checked Oct 28, 2026

80
Needs Work
Performance
FCP
2.96 s
First Contentful Paint
LCP
3.55 s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
14 ms
Total Blocking Time
SI
5.91 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://homivas.shop/
Final URL: https://homivas.shop/
Black Friday sale
Jacket-1
Response
HTTP 200
HTML body
600.9 KB
Compressed
100.1 KB
Links
154 internal · 6 external
Detected technologies
vuenginxangular
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: eefdaf6c6036074c372569df0d21881caffbef824f7e099225a91d765ba30d33
Open Graph title: Black Friday sale
Open Graph description: Jacket-1
Twitter card: summary_large_image
Saved response-header values · 9
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Wed, 28 Oct 2026 22:14:15 GMT
Execution-Time
0.0778901577
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-trace-id
3EAB9BC6-56B6-E951-AD6C-19A79DE79F5C

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

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

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

Open this scan on URLScan 01a184a8-6734-723d-b4e8-e0996cd4fa2c ↗

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations15

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
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:55:52.000000
    Evidence SHA-256
    8e16089428f2c6823d124324a4b706d74976ded8fdc28ff8d6d8102b5903894a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:55:52
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:55:52.000000
    Evidence SHA-256
    8e16089428f2c6823d124324a4b706d74976ded8fdc28ff8d6d8102b5903894a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:55:52
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:05:49.000000
    Evidence SHA-256
    48a7834a562850dec8d316fc5b2e57f12d6bb45a5041a0f93506643c51dad1ee
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:05:49
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:05:49.000000
    Evidence SHA-256
    48a7834a562850dec8d316fc5b2e57f12d6bb45a5041a0f93506643c51dad1ee
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:05:49
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:36.000000
    Evidence SHA-256
    b272c21410fac1c5e3929c256643b74d44e23c6767b84af956cc13c91dc5a043
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:36
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:36.000000
    Evidence SHA-256
    b272c21410fac1c5e3929c256643b74d44e23c6767b84af956cc13c91dc5a043
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:36
    Evidence reason
    alive_content
  7. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:06:56.000000
    Evidence SHA-256
    f77c6283b2cc872f5103ef5f8cec2c9766b9672038ac6bd1fc90152406029648
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:06:56
    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-30 00:06:56.000000
    Evidence SHA-256
    f77c6283b2cc872f5103ef5f8cec2c9766b9672038ac6bd1fc90152406029648
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:06:56
    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
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:18.000000
    Evidence SHA-256
    dc792274352d66bc5f4312ee9f5aa63173e492c272e2eebe3ea4aca7ac1dd8b3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:18
    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-29 12:07:18.000000
    Evidence SHA-256
    dc792274352d66bc5f4312ee9f5aa63173e492c272e2eebe3ea4aca7ac1dd8b3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:18
    Evidence reason
    alive_content
  12. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:20:32.000000
    Evidence SHA-256
    c2cf77834f4140bc57175a0256112158e5b0ad0426fff0771cef9988aacf44d4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:20:32
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:20:32.000000
    Evidence SHA-256
    c2cf77834f4140bc57175a0256112158e5b0ad0426fff0771cef9988aacf44d4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:20:32
    Evidence reason
    alive_content
  15. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 23:15:28.155786
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 13. 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
    homivas.shop detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 82
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 19/92
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as malware, Security threats, Security Risks
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Tencent. Abuse contacts: 1.
    • abuse@tencent.com
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

7 entries
  1. Abuse report sent

    PD-9667B3CFE0656B89488A · Receipt 84129

    abuse@tencent.com
  2. AlienVault OTX

    4 community references

    View source
  3. URLScan

    Page captured

    View source
  4. Cloudflare Radar

    Phishing

    View source
  5. Wayback Machine

    Page archived

    View source
  6. Added to PhishDestroy

    homivas.shop

    View source
  7. VirusTotal

    19/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

Check for cloaking

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

homivas.shop

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 19 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Malicious OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-9667B3CFE0656B89488A Recipient: abuse@tencent.com
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including homivas.shop)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

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/homivas.shop"
  title="PhishDestroy threat report for homivas.shop"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>