Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 6/92 engines flagged. malicious: 4. suspicious: 2. Analysis time (as stored): 2026-11-01T00:50:40Z. Retrieved (as stored): 2026-11-01T03:11:12Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
new-conversation173.shop favicon

new-conversation173.shop

In short

The captured page at new-conversation173.shop presents itself as an article index built around video reviews, with a heading carrying the domain and a tagline promising topic breakdowns, key takeaways and answers to common questions. The visible content is sparse: no article listings appear beneath the tagline, and the only interaction offered is a footer row of three links labeled RSS, llms.txt and Sitemap, alongside a copyright line bearing the domain.

“new-conversation173.shop”

Review the evidence
Registrar
SwedenNameSilo
Resolved IP
Moldova37.221.67.157Alexhost SRL · CDN
Registered
Jul 8, 2026
First observed
Nov 1, 2026
PhishDestroy assessment Critical
85/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 6/92 Spamhaus DBL: phishing domain
VirusTotal
6 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 93
Page captures
6
open gallery
Domain age
122 days
registered 2026-07-08 according to WHOIS
OTX: 1 ref Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded new-conversation173.shop on 2026-11-01. Stored VirusTotal result: 6/92 engines flagged. malicious: 4. suspicious: 2. Analysis time (as stored): 2026-11-01T00:50:40Z. Retrieved (as stored): 2026-11-01T03:11:12Z. Risk: critical (85/100). Registrar: NameSilo. Status: Last known active. Hosting: Alexhost SRL. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
6 / 92
Hosting
Moldova37.221.67.157Alexhost SRL · CDN
Registrar
SwedenNameSilo
Registered
Jul 8, 2026
OTX
1 community ref
Page captures
6
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-01T03:12:58Z
SHA-256: a861f884d87bbdad2d8828b08b8e985bfeed832c4302ae400bc84a770fb998e0

PhishDestroy analysis, reviewed version

The captured page at new-conversation173.shop presents itself as an article index built around video reviews, with a heading carrying the domain and a tagline promising topic breakdowns, key takeaways and answers to common questions. The visible content is sparse: no article listings appear beneath the tagline, and the only interaction offered is a footer row of three links labeled RSS, llms.txt and Sitemap, alongside a copyright line bearing the domain.

The stored VirusTotal domain result reports 6 detections out of 92 engines. DNS8 reported "suspicious"; VIPRE reported "phishing".

Source evidenceVirusTotal 6 / 92 · OTX 1 references 8 sources

VirusTotal

6 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
4
Suspicious
2
Undetected
31

Vendor labels

DNS8
suspicious
VIPRE
phishing
SOCRadar
phishing
LevelBlue
suspicious
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    kurt.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    selah.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    kurt.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    37.221.67.157
  • TTL, seconds
    300
    Type
    MX
    Value
    mail.new-conversation173.shop
    Priority
    1

DNS records observed

JARM fingerprint

28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d

Certificate

Subject alternative names
  • new-conversation173.shop
  • www.new-conversation173.shop
Issuer
Let's Encrypt / YE1
Serial
617dcefecb7028a74b68f5d1e8260ea868e
SHA-256
4b5b67163de4f8fa054c5a2767b30a2a9df680515872605ccbfcd22f830119b6
Subject
new-conversation173.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 4,
    "suspicious": 2,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "VIPRE": "phishing",
    "SOCRadar": "phishing",
    "LevelBlue": "suspicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
First seen
2026-07-08T22:01:03Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "kurt.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "selah.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kurt.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "37.221.67.157"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mail.new-conversation173.shop",
        "priority": 1
    }
]
Dns at
2026-11-01T00:55:38Z
Jarm
28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "new-conversation173.shop",
        "www.new-conversation173.shop"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "617dcefecb7028a74b68f5d1e8260ea868e",
    "sha256": "4b5b67163de4f8fa054c5a2767b30a2a9df680515872605ccbfcd22f830119b6",
    "subject": "new-conversation173.shop",
    "valid_to": "2027-01-29T01:28:41Z",
    "valid_from": "2026-10-31T01:28:42Z"
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
6
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","DNS8","Gridinsoft","LevelBlue","SOCRadar","VIPRE"]
observed_at
2026-11-01 00:50:40
checked_at
2026-11-01 04:11:35
fetched_at
2026-11-01 03:11:35
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

5680ea38-a3a8-4980-ad0b-627a3e66a4cf

Final URL

https://new-conversation173.shop/

HTTP response

200

Navigation history

  • URL
    https://new-conversation173.shop/
    Status
    200

DOM structure hash

b732342fe7bdd75c84c2ea688e8a090b5a0b1beabfffa5c880ee0f62af3646aa

Document hash

7ef2d3d9abf2cd98798571ce76d5d4b56b5270e530c6f372500c783a937c8c36

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    new-conversation173.shop
    Type
    A
    Value
    37.221.67.157

DNSSEC valid

No

IP address

127.0.1.12

127.0.1.12 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
5680ea38-a3a8-4980-ad0b-627a3e66a4cf
Final url
https://new-conversation173.shop/
Status
200
History
[
    {
        "url": "https://new-conversation173.shop/",
        "status": 200
    }
]
DOM structure hash
b732342fe7bdd75c84c2ea688e8a090b5a0b1beabfffa5c880ee0f62af3646aa
Document hash
7ef2d3d9abf2cd98798571ce76d5d4b56b5270e530c6f372500c783a937c8c36
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "new-conversation173.shop",
        "type": "A",
        "value": "37.221.67.157"
    }
]
Dnssec valid
false
Ip
127.0.1.12

127.0.1.12 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 93

SHA-256 80b598c9736dce266be83dccd05821cc8a6923a43283d1dd604c37164187ebd4

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a1951f-c431-73d9-a1f4-0bce7fe513b1

Final URL

https://new-conversation173.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://new-conversation173.shop/
    From
    http://new-conversation173.shop/
    Status
    307

IP address

37.221.67.157

Reverse DNS (PTR)

vps3

Contacted IP addresses

  • 37.221.67.157

Autonomous systems (ASN)

  • 200019

Server countries

  • MD

Document hash

7ef2d3d9abf2cd98798571ce76d5d4b56b5270e530c6f372500c783a937c8c36

TLS session and certificate

Subject alternative names
  • new-conversation173.shop
  • www.new-conversation173.shop
Cipher
AES_256_GCM
Issuer
YE1
Subject
new-conversation173.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

115

Registered domain age, days

115

Certificate age, days

1

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
nginx/1.24.0 (Ubuntu)
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a1951f-c431-73d9-a1f4-0bce7fe513b1
Final url
https://new-conversation173.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://new-conversation173.shop/",
        "from": "http://new-conversation173.shop/",
        "status": 307
    }
]
Ip
37.221.67.157
Ptr
vps3
Contacted IP addresses
[
    "37.221.67.157"
]
Asns
[
    "200019"
]
Countries
[
    "MD"
]
Document hash
7ef2d3d9abf2cd98798571ce76d5d4b56b5270e530c6f372500c783a937c8c36
Tls
{
    "san": [
        "new-conversation173.shop",
        "www.new-conversation173.shop"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YE1",
    "subject": "new-conversation173.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-29T01:28:41Z",
    "valid_from": "2026-10-31T01:28:42Z"
}
Domain age days
115
Apex age days
115
Tls age days
1
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.24.0 (Ubuntu)",
    "content-type": "text/html; charset=utf-8"
}

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
new-conversation173.shop video review article index page
ai_description
PhishDestroy records the video-review article index page captured at new-conversation173.shop, showing its topic breakdowns and footer links.
ai_summary
The captured page at new-conversation173.shop presents itself as an article index built around video reviews, with a heading carrying the domain and a tagline promising topic breakdowns, key takeaways and answers to common questions. The visible content is sparse: no article listings appear beneath the tagline, and the only interaction offered is a footer row of three links labeled RSS, llms.txt and Sitemap, alongside a copyright line bearing the domain. The stored VirusTotal domain result reports 6 detections out of 92 engines. DNS8 reported "suspicious"; VIPRE reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 04:20:11
revision
e864952aecdd18777b7880217e7b40a50fe389cfbc263136251c1b364b767b79
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

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

Mail configuration

MX records
  • mail.new-conversation173.shop
SPF lookups
0

CAA records

Domain
new-conversation173.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Trackers

Requests
3

DNS servers

Nameservers
  • IP address
    162.159.38.21
    Host
    selah.ns.cloudflare.com
  • IP address
    173.245.59.193
    Host
    kurt.ns.cloudflare.com
DNS zone
new-conversation173.shop

Location

IP address
37.221.67.157
ASN
200019
Organization
Alexhost SRL
City
Chisinau
Country
MD

DNS records

A
  • 37.221.67.157
MX
  • Mail server
    mail.new-conversation173.shop
    Priority
    1
NS
  • selah.ns.cloudflare.com
  • kurt.ns.cloudflare.com
SOA
Primary nameserver
kurt.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418669907
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
37.221.67.157
IP version
4
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mail.new-conversation173.shop"
    ],
    "spf_lookups": 0
}
Caa records
{
    "domain": "new-conversation173.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-01T03:09:50Z",
    "first": "2026-11-01T03:09:50Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2782
}
Trackers
{
    "requests": 3
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.38.21",
            "host": "selah.ns.cloudflare.com"
        },
        {
            "ip": "173.245.59.193",
            "host": "kurt.ns.cloudflare.com"
        }
    ],
    "zone": "new-conversation173.shop"
}
Location
{
    "ip": "37.221.67.157",
    "asn": "200019",
    "org": "Alexhost SRL",
    "city": "Chisinau",
    "country": "MD"
}
DNS records
{
    "A": [
        "37.221.67.157"
    ],
    "MX": [
        "{\"exchange\": \"mail.new-conversation173.shop\", \"priority\": 1}"
    ],
    "NS": [
        "selah.ns.cloudflare.com",
        "kurt.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"kurt.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418669907, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "37.221.67.157",
    "family": 4
}
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation
CF Cloudflare Radar Verdict Malicious
Security threats Malware Malware
View full Cloudflare Radar report

Questions about new-conversation173.shop

Is new-conversation173.shop legit?

PhishDestroy rates new-conversation173.shop as critical risk (85/100) from the recorded evidence; it was first recorded on 2026-11-01. Stored VirusTotal result: 6/92 engines flagged. malicious: 4. suspicious: 2. Analysis time (as stored): 2026-11-01T00:50:40Z. Retrieved (as stored): 2026-11-01T03:11:12Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is new-conversation173.shop safe to connect a wallet?

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

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

Explore

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

Checked, no match

Last checked

Stored Capture · 6 captures

Cloudflare Radar 1 / 6 Used in the analysis Source file SHA-256: a861f884d87bbdad2d8828b08b8e985bfeed832c4302ae400bc84a770fb998e0 SHA-256 of the prepared copy given to the model: f2462964745149799e6ad2cc32800bc28a8beb72eac1928b8e88c6034331e6eb
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://new-conversation173.shop/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
new-conversation173.shop
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 81 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 93 report ↗
IP Context Moldova37.221.67.157 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NameSilo SE(SE) PhishDestroy Investigation
Abuse contactabuse@alexhost.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for new-conversation173.shop →
Hosting abuse contact abuse@alexhost.com Alexhost SRL · AS200019
RegistrationCreated Jul 8, 2026 (122d) — Expires Jul 8, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://new-conversation173.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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

Accreditation is a contract, not a safety certification.

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

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

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Moldova37.221.67.157
Network ASN
AS200019
Organization
Alexhost SRL
Observed location
MoldovaChisinau, MD
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • kurt.ns.cloudflare.com
  • selah.ns.cloudflare.com

SOA

  • nsname: kurt.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418669907
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Mail routing 1 MX record

  • mail.new-conversation173.shoppriority 1

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-31 01:28:42
Valid until
2027-01-29 01:28:41
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint4b5b67163de4f8fa054c5a2767b30a2a9df680515872605ccbfcd22f830119b6
Certificate names · 2 SANs
  • new-conversation173.shop
  • www.new-conversation173.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 · 37.221.67.157rapiddns.io

Latest Classified Outcome 2026-11-07 23:06:42 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-11-07 23:06:42 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 23:27:57 UTC last content: 2026-11-07 23:06:42 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.new-conversation173.shopDomain record
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
DNS8
VIPRE
SOCRadar
LevelBlue
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of new-conversation173.shop · checked Nov 1, 2026

90
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
18.46 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://new-conversation173.shop/
Final URL: https://new-conversation173.shop/
new-conversation173.shop
Articles based on video reviews: topic breakdowns, key takeaways and answers to common questions.
Response
HTTP 200
HTML body
6.6 KB
Compressed
2.2 KB
Links
4 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.24.0 (Ubuntu)
Content-Type: text/html; charset=utf-8
Cache-Control: public, max-age=600, must-revalidate
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: new-conversation173.shop
Open Graph description: Articles based on video reviews: topic breakdowns, key takeaways and answers to common questions.
Twitter card: summary
Saved response-header values · 9
Cache-Control
public, max-age=600, must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 01 Nov 2026 03:12:50 GMT
Etag
W/"6ae551e2-1a4a"
Last-Modified
Sat, 31 Oct 2026 02:26:42 GMT
Server
nginx/1.24.0 (Ubuntu)
Transfer-Encoding
chunked

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: 4 SHA-256 hashes: 4 URLScan scan:

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

Open this scan on URLScan 01a1951f-c431-73d9-a1f4-0bce7fe513b1 ↗

Stored observation history8

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

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 3
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Domain monitor · First collection record

    Reachable

All retained availability observations26

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-11-08 00:06:42.000000
    Evidence SHA-256
    cec2740a9b9f1429bf39068ed512dc82a3ffe92833133abd8137ee79ccb1e938
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:06:42
    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-11-08 00:06:42.000000
    Evidence SHA-256
    cec2740a9b9f1429bf39068ed512dc82a3ffe92833133abd8137ee79ccb1e938
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:06:42
    Evidence reason
    alive_content
  3. 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-11-07 23:22:04.326583
    Evidence SHA-256
    19ed99e260d67463304cd035997394a09991119b8c1f635f2967c41ae291fdce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 23:22:04.326583
    Evidence reason
  4. 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-11-07 12:06:06.000000
    Evidence SHA-256
    e887c32da232427b7ef3aa27f2b2138632d900e10ab89ad5e050fb9b0b47da1b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:06:06
    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-11-07 12:06:06.000000
    Evidence SHA-256
    e887c32da232427b7ef3aa27f2b2138632d900e10ab89ad5e050fb9b0b47da1b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:06:06
    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
    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-11-07 01:25:29.000000
    Evidence SHA-256
    870448c99f4e6455b30ff4e5ab12e068b2a57bc3e5c5399970b9d725c5c48636
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 01:25:29
    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-11-07 01:25:29.000000
    Evidence SHA-256
    870448c99f4e6455b30ff4e5ab12e068b2a57bc3e5c5399970b9d725c5c48636
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 01:25:29
    Evidence reason
    alive_content
  8. 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-11-06 23:21:40.556826
    Evidence SHA-256
    2071dfbc1c6ae55fbd72318bd0bd5b8ac6720ae3a22d4fd33ac3fef7bf7b47da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 23:21:40.556826
    Evidence reason
  9. 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-11-05 23:21:20.401484
    Evidence SHA-256
    6561edb8793c530bd35b9930c0ef92bee67e8e1395a2c6e53ebfe984a32e4303
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 23:21:20.401484
    Evidence reason
  10. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 01:10:29.000000
    Evidence SHA-256
    962fb0ec7b59b156b4c143960debd8aa941a856144d46c40167415526effc5eb
    Evidence timestamp as recorded
    2026-11-05 01:10:29
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  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-11-05 01:10:29.000000
    Evidence SHA-256
    e4da6a482906375133626ffa19fd943ac1c43934bdd69805a2cb25eb2a98484c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:10:29
    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-11-04 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    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-11-04 13:12:04.000000
    Evidence SHA-256
    4af5417905c84543388bbd4477202e220e23c97b4a1435c7e9e5c0611caf5809
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:12:04
    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-11-04 13:12:04.000000
    Evidence SHA-256
    4af5417905c84543388bbd4477202e220e23c97b4a1435c7e9e5c0611caf5809
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:12:04
    Evidence reason
    alive_content
  15. 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-11-03 23:21:00.551669
    Evidence SHA-256
    93de4ce3edcedd421525733b44961d482bf295f4b8d35b7851f110ca6f86698b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:21:00.551669
    Evidence reason
  16. 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-11-02 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  17. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:32.000000
    Evidence SHA-256
    10cdebc2bcae5b58b954ebcfcfbad9ac98b6729341f4214a8ee59c288aaa9e24
    Evidence timestamp as recorded
    2026-11-02 12:31:32
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  18. 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-11-02 12:31:32.000000
    Evidence SHA-256
    690ca00c8da8b149c5bd972988625cf6619fba1e271a5475ea425665add4ad0a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:32
    Evidence reason
    alive_content
  19. 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-11-02 00:33:10.000000
    Evidence SHA-256
    adc577f6c67fc801d5961c6bf132bf271c9fe0349a95ea89b8bc9677a77b2b4f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:33:10
    Evidence reason
    alive_content
  20. 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-11-02 00:33:10.000000
    Evidence SHA-256
    adc577f6c67fc801d5961c6bf132bf271c9fe0349a95ea89b8bc9677a77b2b4f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:33:10
    Evidence reason
    alive_content
  21. 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-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  22. 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-11-01 12:35:09.000000
    Evidence SHA-256
    fc42056ff04a3dc763d448fba96540e971f200af80a5ec4efc8255f3a3ec9a21
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:35:09
    Evidence reason
    alive_content
  23. 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-11-01 12:35:09.000000
    Evidence SHA-256
    fc42056ff04a3dc763d448fba96540e971f200af80a5ec4efc8255f3a3ec9a21
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:35:09
    Evidence reason
    alive_content
  24. 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-11-01 04:22:51.000000
    Evidence SHA-256
    56ef50e8b8e4eeb340f968d00b00d0ebec4c3b55ff92d37182ad90a169b8cb51
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 04:22:51
    Evidence reason
  25. 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-11-01 04:22:51.000000
    Evidence SHA-256
    56ef50e8b8e4eeb340f968d00b00d0ebec4c3b55ff92d37182ad90a169b8cb51
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 04:22:51
    Evidence reason
  26. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:12:19.466817
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 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
    new-conversation173.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 · Registrar Context: NameSilo · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 11 of 11
  • 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: 93
  • 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: 6/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Security threats, malware
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    new-conversation173.shop

    View source
  5. VirusTotal

    6/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

new-conversation173.shop

Evidence & External Reports

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

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

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

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

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