PhishDestroy first recorded booknookstore.shop on 2026-10-24. Stored VirusTotal result: 4/92 engines flagged. Malicious: 2. Suspicious: 2. Analysis time (as stored): 2026-10-24 23:21 UTC. Retrieved (as stored): 2026-10-24 23:26 UTC.
Page title: “Book Nook Boutique – Kreative Booknooks in Deutschland | Booknook”
More about the sources
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. Malicious: 2. Suspicious: 2. Analysis time (as stored): 2026-10-24 23:21 UTC. Retrieved (as stored): 2026-10-24 23:26 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@rashost.com. The latest stored availability evidence still shows the domain reachable; 28 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
28 days
Reports sent
1
Latest case ID
PD-20261024-2C8B4B
Current status
HTTP 200 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded booknookstore.shop on 2026-10-24. Stored VirusTotal result: 4/92 engines flagged. Malicious: 2. Suspicious: 2. Analysis time (as stored): 2026-10-24 23:21 UTC. Retrieved (as stored): 2026-10-24 23:26 UTC. Risk: critical (evidence score 90/100). Registrar: Dynadot. Status: Last known active. Hosting: malakmadze Malakmadze Web LLC, GE. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
PhishDestroy’s intake AI classified booknookstore.shop as malicious because the site claims to sell “Book Nooks” at deep discounts while the displayed customer reviews mention unrelated clothing items, a mismatch that suggests copied generic content and brand impersonation. The assessment also noted the use of a cheap .shop TLD combined with the Booknook name, a pattern frequently seen in fake‑shop pages. The domain was first observed by PhishDestroy on 2026-10-25 and a page fetch on 2026-10-24 returned an HTTP 200 response after a 307 redirect from http to https.
How the scam works
Fake‑shop phishing sites lure visitors with steep price cuts, then harvest payment details, login credentials or other personal information entered during a checkout flow. They typically reuse generic e‑commerce templates and fabricated reviews to appear legitimate.
Evidence
VirusTotal scanned the domain on 2026-10-25 and reported four detections from 92 engines, with G‑Data labeling it malware and LevelBlue labeling it phishing while two other engines marked it suspicious. URLScan captured the site on the same day and returned a malicious verdict with a perfect 100 score, categorising it as phishing and tagging it as a fake shop. PhishDestroy’s internal blocklist includes the domain (checked 2026-10-25); Google Safe Browsing (checked 2026-10-24) and Spamhaus DBL (checked 2026-10-25) reported no flag, and OTX listed four pulses referencing the domain on 2026-10-25.
Infrastructure
The domain was registered 171 days before the capture and uses a Let’s Encrypt certificate issued on 2026-09-08, valid until 2026-12-07. DNS is served by Cloudflare nameservers and resolves to IP 46.245.239.153, which belongs to ASN 199242 (Malakmadze Web LLC) in Georgia; open ports observed were 22, 80, 443 and 8000.
What to do
Avoid entering any payment, login or personal information on the site and, if such data was submitted, change the associated passwords and monitor financial accounts for unauthorized activity. Defenders should block the domain at the network perimeter and review logs for any connections to the recorded IP address.
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.
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
booknookstore.shop — Fake Booknook Store Phishing
AI description
PhishDestroy flagged booknookstore.shop as a malicious fake‑shop phishing site impersonating Booknook, citing mismatched product content and AI‑detected risk.
AI summary
Overview PhishDestroy’s intake AI classified booknookstore.shop as malicious because the site claims to sell “Book Nooks” at deep discounts while the displayed customer reviews mention unrelated clothing items, a mismatch that suggests copied generic content and brand impersonation. The assessment also noted the use of a cheap .shop TLD combined with the Booknook name, a pattern frequently seen in fake‑shop pages. The domain was first observed by PhishDestroy on 2026-10-25 and a page fetch on 2026-10-24 returned an HTTP 200 response after a 307 redirect from http to https. How the scam works Fake‑shop phishing sites lure visitors with steep price cuts, then harvest payment details, login credentials or other personal information entered during a checkout flow. They typically reuse generic e‑commerce templates and fabricated reviews to appear legitimate. Evidence VirusTotal scanned the domain on 2026-10-25 and reported four detections from 92 engines, with G‑Data labeling it malware and LevelBlue labeling it phishing while two other engines marked it suspicious. URLScan captured the site on the same day and returned a malicious verdict with a perfect 100 score, categorising it as phishing and tagging it as a fake shop. PhishDestroy’s internal blocklist includes the domain (checked 2026-10-25); Google Safe Browsing (checked 2026-10-24) and Spamhaus DBL (checked 2026-10-25) reported no flag, and OTX listed four pulses referencing the domain on 2026-10-25. Infrastructure The domain was registered 171 days before the capture and uses a Let’s Encrypt certificate issued on 2026-09-08, valid until 2026-12-07. DNS is served by Cloudflare nameservers and resolves to IP 46.245.239.153, which belongs to ASN 199242 (Malakmadze Web LLC) in Georgia; open ports observed were 22, 80, 443 and 8000. What to do Avoid entering any payment, login or personal information on the site and, if such data was submitted, change the associated passwords and monitor financial accounts for unauthorized activity. Defenders should block the domain at the network perimeter and review logs for any connections to the recorded IP address. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17003-33aa-77cc-b59d-535cebbd514f/ Cloudflare Radar report: https://radar.cloudflare.com/scan/469a4158-1f05-4f10-b948-1058d53e192e URLQuery report: https://urlquery.net/report/c184dd0f-c0e1-42c0-908e-31e894238ea9 Stored capture screenshot: https://i.ibb.co/zVLQssfK/f9164a39bfa8.png Cloudflare Radar screenshot (2026-10-24T22:57:01Z): https://screenshots.phishdestroy.io/cf/469a4158-1f05-4f10-b948-1058d53e192e.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/c184dd0f-c0e1-42c0-908e-31e894238ea9.png URLScan screenshot (2026-10-24T22:29:10Z): https://screenshots.phishdestroy.io/us/01a17008-172e-71a3-a0ca-d58b2a2ddce8.png URLScan capture report: https://urlscan.io/result/01a17008-172e-71a3-a0ca-d58b2a2ddce8/ VirusTotal report: https://www.virustotal.com/gui/domain/booknookstore.shop Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=booknookstore.shop Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
This website does not have many visitors We found many low rated websites on the same server We could not analyze the content of the site
According to the SSL check the certificate is valid
Questions about booknookstore.shop
Is booknookstore.shop legit?
PhishDestroy rates booknookstore.shop as critical risk (evidence score 90/100) from the recorded evidence; it was first recorded on 2026-10-24. Stored VirusTotal result: 4/92 engines flagged. Malicious: 2. Suspicious: 2. Analysis time (as stored): 2026-10-24 23:21 UTC. Retrieved (as stored): 2026-10-24 23:26 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is booknookstore.shop safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on booknookstore.shop. A confirmed blockchain transaction cannot be reversed.
What should I do if I used booknookstore.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.
IP Reputation46.245.239.1530/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing.0 reportschecked 2026-10-25
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
46.245.239.153
Network ASN
AS199242
AS name
malakmadze Malakmadze Web LLC, GE
Organization
Malakmadze Web LLC
Observed location
Los Angeles, GE
Nameservers 2
doug.ns.cloudflare.com
val.ns.cloudflare.com
SOA
nsname: doug.ns.cloudflare.com
hostmaster: dns.cloudflare.com
serial: 2417973015
refresh: 10000
retry: 2400
expire: 604800
minttl: 1800
Location describes the IP network.
TLS certificate
Issuer
YE2
Valid from
2026-09-08 19:17:39
Valid until
2026-12-07 19:17:38
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3cdbdbbfd91fc45b234c1c2dd208ab539e4e58da3aed5873085fd66a3cc68b43Certificate names · 1 SAN
booknookstore.shop
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:16 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:16 UTClast content: 2026-11-22 11:16 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.
img.booknookstore.shopDomain record
Technologies · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
HSTS: not observedDNSSEC: not observedWAF / firewall: observedCloaking flag: not observed
Open Graph title:Book Nook Boutique – Kreative Booknooks in Deutschland
Open Graph description:Booknooks bei Booknook! Versandkostenfrei ab 30 €! ✅Weltweit kuratiertes Sortiment; ✅Engagierter Support; ✅Gratis Ersatzteile; ✅60 Tage Rückgaberecht.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:58 UTC.
Recorded events: 18. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
booknookstore.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 · Site Came Back Online · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailablerecorded
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
5 entries
Lifecycle
Domain registered
Added to PhishDestroy+171 d 4 h
First abuse report sent+5 min
VirusTotal analysis with detections+49 min
Reported 171 d 4 h after registration
AlienVault OTX
4 community references
+5 min
VirusTotal
4/92 engine detections
+49 min
Abuse report sent
PD-20261024-2C8B4B · Receipt 82576
abuse@rashost.com
+5 min
Added to PhishDestroy
booknookstore.shop
same minute
URLScan
Page captured
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches1
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
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.
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 booknookstore.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)
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
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.