URLScan
Malicious
SHA-256 074dda5f…d20c100
PhishDestroy records brecksdirect.shop as a storefront page offering Dutch bulbs and perennials, with product categories, search, account, and cart features.
Page title: “Flower Bulbs - Dutch Bulbs Since 1818 | Breck's”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
URLScan capture · 2026-05-12 12:15 UTC · SHA-256 a5f6eee4…7b04ce2
PhishDestroy analysis, reviewed version
On 2026-05-12, brecksdirect.shop displayed a garden retail storefront branded as Breck's, with a logo reading "Direct to you from Holland since 1886." The page features a search bar, account and cart links, and a navigation menu listing categories such as New, Spring-Planted Bulbs, Fall-Planted Bulbs, Sun Perennials, Shade Perennials, Garden Essentials, Gifts, and Sale. A hero banner over a flower field reads "Straight From Holland to Your Garden" and "Shop premium Dutch bulbs and perennials shipped directly from our fields to your front door," with a Shop Now button, followed by a "Why Choose Us" section.
The stored VirusTotal domain result reports 0 detections out of 92 engines.
Malicious
SHA-256 074dda5f…d20c100
4 community references
Open reportScan report
Open reportObserved: · Retrieved:
127.0.1.48 is not a public internet address. It is the value stored in this source record, not the site's hosting address.
| UUID | 72ce88c1-3fd4-48d6-b151-c9480fc2beaa |
|---|---|
| Final URL | https://brecksdirect.shop/ |
| Status | 200 |
| History | URL: https://brecksdirect.shop/; Status: 200 |
| DOM structure hash | 9b84f3f27d1bede1b9f6cb640295421e6070522235c0511700b15e8252bb7e3f |
| Document hash | b2a6985d71ce8653d6ef67d3266e1a668c08ea89a77e10e4fac5459011fd9fb3 |
| Radar rank | Bucket: >200000 |
| DNS records | Name: brecksdirect.shop; Type: A; Value: 46.245.239.153 |
| Dnssec valid | ✗ |
| IP | 127.0.1.48 127.0.1.48 is not a public internet address. It is the value stored in this source record, not the site's hosting address. |
84/100
Trust score, lower = worse
Open reportNarrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Trackers | Requests: 46; 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: 172.64.33.159; Host: doug.ns.cloudflare.com), (IP: 108.162.192.234; Host: val.ns.cloudflare.com); Zone: brecksdirect.shop |
| Location | IP: 46.245.239.153; ASN: 219278; Org: Beijing Ruihao Kai Yuan Technology Co., Ltd; City: Washington; Country: US |
| SSL | Issuer: Let's Encrypt / YE1; Subject: brecksdirect.shop |
| DNS records | A: 46.245.239.153; NS: val.ns.cloudflare.com, doug.ns.cloudflare.com; Soa: Nsname: doug.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419293852; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: SAMEORIGIN; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: 1; mode=block; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 46.245.239.153; Family: 4 |
| Tech stack | Technologies: Node.js, Headless UI, React, Next.js, Priority Hints, Google Font API, Webpack, Prism, Open Graph, Module Federation, HTTP/3 |
| HTTP headers | Headers: Content type: text/html; charset=utf-8; X frame options: SAMEORIGIN; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin; Via: 1.1 Caddy |
a5f6eee4…7b04ce2 SHA-256 of the prepared copy given to the model: ec638f52…9ec10b2 a5f6eee4621645831fb411201c18c218f53b4655f73c53d8159a34fc07b04ce2 · 496012 bytes 86eb695470b88a021f74429bf8b534744dfacd915679b01cb19fa25c57e9bd2a · 4143 bytes 86eb695470b88a021f74429bf8b534744dfacd915679b01cb19fa25c57e9bd2a · 4143 bytes 86eb695470b88a021f74429bf8b534744dfacd915679b01cb19fa25c57e9bd2a · 4143 bytes 86eb695470b88a021f74429bf8b534744dfacd915679b01cb19fa25c57e9bd2a · 4143 bytes 9731da422893a1622f762e63bb52adac6cfd14b5a8e676b4bc6442072a3b8288 · 1532798 bytes 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.
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.
Edge-IP reputation is not attributed to this domain.
val.ns.cloudflare.comdoug.ns.cloudflare.comnsname: doug.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2419293852refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
5064ba971c687b7382e361e01d62de6826911ee97ed8750e634e295b76bbe360brecksdirect.shopSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was reachable but behind an access challenge at the latest check.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
img.brecksdirect.shopDomain recordwww.brecksdirect.shopDomain recordGoogle PageSpeed Insights — mobile performance audit of brecksdirect.shop ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 60 SHA-256 hashes: 51 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-06 20:26 UTC.
Open this scan on URLScan 019e1c1c-7c3f-752a-a348-cf747f240cdd ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
brecksdirect.shop Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
brecksdirect.shop)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.