Skip to security report
brecksshop.shop favicon
Domain security and threat intelligence

brecksshop.shop

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

On 2026-10-02, brecksshop.shop was captured showing a storefront homepage branded with the Breck's logo and the tagline "Direct to you from Holland since 1886." The page features a large hero image of a tulip field with the headline "Straight from Holland's Finest Fields," describing premium Dutch flower bulbs and perennials delivered to the door, alongside a "Shop Now" button. Navigation categories include bulbs, perennials, garden essentials, and gifts, with a cart indicator showing zero items.

Page title: “Flower Bulbs - Dutch Bulbs Since 1818 | Breck's”

More about the sources
Recorded security signals

Stored VirusTotal result: 3/92 engines flagged. Malicious: 0. Suspicious: 3. Analysis time (as stored): 2026-11-06 17:56 UTC. Retrieved (as stored): 2026-11-06 20:25 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 3/92
Registrar
United StatesDynadot
Resolved IP
China185.234.12.89Malakmadze Web LLC
Registered
2026-07-16
First seen by PhishDestroy
2026-11-05
OTX
community references
Page captures
open gallery
OTX: 4 refs 2026-11-05

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded brecksshop.shop on 2026-11-05. Stored VirusTotal result: 3/92 engines flagged. Malicious: 0. Suspicious: 3. Analysis time (as stored): 2026-11-06 17:56 UTC. Retrieved (as stored): 2026-11-06 20:25 UTC. Risk: critical (evidence score 80/100). Registrar: Dynadot. Status: Last known active. Hosting: Malakmadze Web LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
3 / 92
Hosting
China185.234.12.89Malakmadze Web LLC
Registrar
United StatesDynadot
Registered
2026-07-16
OTX
4 community refs
Page captures
7

URLScan capture · 2026-10-02 16:20 UTC · SHA-256 99ad1e96…632213c

PhishDestroy analysis, reviewed version

On 2026-10-02, brecksshop.shop was captured showing a storefront homepage branded with the Breck's logo and the tagline "Direct to you from Holland since 1886." The page features a large hero image of a tulip field with the headline "Straight from Holland's Finest Fields," describing premium Dutch flower bulbs and perennials delivered to the door, alongside a "Shop Now" button. Navigation categories include bulbs, perennials, garden essentials, and gifts, with a cart indicator showing zero items.

The stored VirusTotal domain result reports 3 detections out of 92 engines. SOCRadar reported "suspicious"; Gridinsoft reported "suspicious".

Source evidenceVirusTotal 3 / 92 · OTX 4 references 6 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 8 fields
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
Result state
observed
Numerator
6
Denominator
92
Vendors
alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, Netcraft, SOCRadar
Checked at
2026-11-14 04:12:17
Fetched at
2026-11-14 03:12:17

URLScan

Malicious

SHA-256 4f0137a7…c415cf7

Open report
URLScanOriginal source recordObserved: 23 fields

OTX

4 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

ee9cd015-74c4-457e-825a-b71579f37e57

Final URL

https://brecksshop.shop/

HTTP response

200

Navigation history

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

DOM structure hash

d159b41b3148279a996fa4dcc18ee23ce4d731900ce81f8cb8907bb9ea15b396

Document hash

4c17dc737a40d94948c7bd01ca4308e32358e8039bde3a90c250a66affae01ef

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    brecksshop.shop
    Type
    A
    Value
    185.234.12.89

DNSSEC valid

✗

IP address

127.0.1.18

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

Original source fields · JSON
UUID
ee9cd015-74c4-457e-825a-b71579f37e57
Final URL
https://brecksshop.shop/
Status
200
History
URL: https://brecksshop.shop/; Status: 200
DOM structure hash
d159b41b3148279a996fa4dcc18ee23ce4d731900ce81f8cb8907bb9ea15b396
Document hash
4c17dc737a40d94948c7bd01ca4308e32358e8039bde3a90c250a66affae01ef
Radar rank
Bucket: >200000
DNS records
Name: brecksshop.shop; Type: A; Value: 185.234.12.89
Dnssec valid
✗
IP
127.0.1.18

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

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Content heuristic only; not the final score

Open report
Technical metadata

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
brecksshop.shop: Recorded Dutch Flower Bulb Storefront Homepage
AI description
PhishDestroy records the captured homepage of brecksshop.shop, showing a Breck's-branded storefront offering Dutch flower bulbs and perennials.
AI summary
On 2026-10-02, brecksshop.shop was captured showing a storefront homepage branded with the Breck's logo and the tagline "Direct to you from Holland since 1886." The page features a large hero image of a tulip field with the headline "Straight from Holland's Finest Fields," describing premium Dutch flower bulbs and perennials delivered to the door, alongside a "Shop Now" button. Navigation categories include bulbs, perennials, garden essentials, and gifts, with a cart indicator showing zero items. The stored VirusTotal domain result reports 3 detections out of 92 engines. SOCRadar reported "suspicious"; Gridinsoft reported "suspicious".
AI generated by
threat-v6-mimo
AI generated at
2026-11-10T16:15:54Z
Revision
61013d62d5e03264eb6b16e5a050735ed518c2029ea4ab5159334bbac29ee187
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: 11 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Trackers

Requests
47
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
DNS zone
brecksshop.shop

Location

IP address
185.234.12.89
ASN
199242
Organization
Malakmadze Web LLC
City
Jingshan
Country
CN

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
brecksshop.shop

DNS records

A
  • 185.234.12.89
NS
  • ns2.dyna-ns.net
  • ns1.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.brecksshop.shop
Serial
2026071503
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
185.234.12.89
IP version
4
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Trackers
Requests: 47; Trackers: (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 1)
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443
DNS server
NS: (IP: 162.159.24.5; Host: ns2.dyna-ns.net), (IP: 162.159.27.158; Host: ns1.dyna-ns.net); Zone: brecksshop.shop
Location
IP: 185.234.12.89; ASN: 199242; Org: Malakmadze Web LLC; City: Jingshan; Country: CN
SSL
Issuer: Let's Encrypt / YE2; Subject: brecksshop.shop
DNS records
A: 185.234.12.89; NS: ns2.dyna-ns.net, ns1.dyna-ns.net; Soa: Nsname: ns1.dyna-ns.net; Hostmaster: hostmaster.brecksshop.shop; Serial: 2026071503; Refresh: 16384; Retry: 2048; Expire: 1209600; Minttl: 300
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Get IP
IP: 185.234.12.89; Family: 4

Questions about brecksshop.shop

Is brecksshop.shop legit?

PhishDestroy rates brecksshop.shop as critical risk (evidence score 80/100) from the recorded evidence; it was first recorded on 2026-11-05. Stored VirusTotal result: 3/92 engines flagged. Malicious: 0. Suspicious: 3. Analysis time (as stored): 2026-11-06 17:56 UTC. Retrieved (as stored): 2026-11-06 20:25 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is brecksshop.shop safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on brecksshop.shop. A confirmed blockchain transaction cannot be reversed.

What should I do if I used brecksshop.shop?

  • 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
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • 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 1
PhishDestroy PhishDestroy list View source

Page captures (7)

All capture links and hashes (7)
Observed page title
Flower Bulbs - Dutch Bulbs Since 1818 | Breck's
Automated brand references
Mantle
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 20 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Fakeshop report ↗
IP Reputation China185.234.12.89 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-11-06
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationCreated 2026-07-16 (129d) — Expires 2027-07-16
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-05
DOM Analysisanalyzed 2026-11-07score 10/1001 brand signal
Submitted URLhttp://brecksshop.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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
China185.234.12.89
Network ASN
AS199242
Organization
Malakmadze Web LLC
Observed location
ChinaJingshan, CN

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.brecksshop.shop
  • serial: 2026071503
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-14 04:11:38
Valid until
2026-12-13 04:11:37
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3d9780495703fed680426b6224130b333a22d3e4ed75acca08ee519a85f114c6
Certificate names · 1 SAN
  • brecksshop.shop

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

Latest Classified Outcome 2026-11-22 11:23 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
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-22 11:23 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:23 UTC last content: 2026-11-22 11:23 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.
Technologies · 6 identified
Open complete records

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy Previous stored snapshot: 3 detections
SOCRadar
Gridinsoft
alphaMountain.ai
PageSpeed (mobile): 96

Google PageSpeed Insights — mobile performance audit of brecksshop.shop ·

96
Good
Performance
FCP
1.91 s
First Contentful Paint
LCP
1.91 s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
136 ms
Total Blocking Time
SI
3.16 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

All stored data107
Open complete records

Captured network requests

Network requests: 52 SHA-256 hashes: 52 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-08 16:30 UTC.

Open this scan on URLScan 01a1bbe3-ada6-772d-9712-5151d2b11ba8 ↗

Stored observation history16
Open complete records
Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-06 17:28:09
All retained availability observations61
Open complete records

Threat Response Pipeline

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

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

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    brecksshop.shop detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+112 d 1 h
  3. VirusTotal analysis with detections+35 h 44 min
  1. AlienVault OTX

    4 community references

    +42 h 26 min
  2. URLScan

    Page captured

    +46 h 6 min
  3. VirusTotal

    3/92 engine detections

    +35 h 44 min
  4. Added to PhishDestroy

    brecksshop.shop

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.

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.

brecksshop.shop

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 brecksshop.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

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.

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/brecksshop.shop"
  title="PhishDestroy threat report for brecksshop.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>