# PhishDestroy threat dossier — thymefoodblog.com ================================================================ Fetched: 2026-07-23 20:48:01 UTC Canonical: https://phishdestroy.io/domain/thymefoodblog.com/ ## VERDICT ---------------------------------------------------------------- CRITICAL THREAT — DO NOT VISIT Composite threat score: 95/100 (PhishDestroy scoring — see methodology below) ## DETECTION EVIDENCE ---------------------------------------------------------------- VirusTotal: 0/91 security vendors flagged this domain Public blocklists: listed on 3 independent blocklists ## INFRASTRUCTURE ---------------------------------------------------------------- IP address: 209.182.224.47 (US, Seattle) ASN: AS395092 Shock Hosting LLC Hosting org: Shock Hosting LLC Registrar: NAMECHEAP INC Nameservers: dns1.registrar-servers.com, dns2.registrar-servers.com Registered: 2026-05-27 Expires: 2027-05-27 Page title: Thyme Food Blog HTTP response: 200 ## TLS CERTIFICATE ---------------------------------------------------------------- Issuer: Let's Encrypt / YR2 Expires: 2026-09-08 Status: INVALID chain Fingerprint: 87e0c7b8fcd030aaaa958fab20311c85c9f455a0a5482067db9a97aefce599d5 Subject Alternative Names (related infrastructure — often same operator): - www.thymefoodblog.com ## ABUSE-REPORT HISTORY (evidence of registrar non-response) ---------------------------------------------------------------- Status: pending notification queue. No abuse reports filed yet — this domain is waiting for the next cycle of our automated abuse-reporter. ## TIMELINE ---------------------------------------------------------------- Domain registered: 2026-05-27 (per WHOIS / CT — may reflect a renewal or transfer date, not first-ever registration) First detected: 2026-07-17 09:08:07 UTC (by PhishDestroy tracker) First reported: 2026-07-17 09:36:59 UTC (abuse notice filed) Last verified: 2026-07-23 20:20:25 UTC Current status: ACTIVE / observable ## EXTERNAL CORROBORATION (third-party evidence) ---------------------------------------------------------------- URLScan.io: https://urlscan.io/result/019f6ee5-e3fc-76b4-80f1-ab32215b4db0/ URLQuery: https://urlquery.net/report/6d707d7c-2691-439a-8df6-1add22f0edfe Wayback Machine: https://web.archive.org/web/*/thymefoodblog.com crt.sh CT logs: https://crt.sh/?q=%25.thymefoodblog.com Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=thymefoodblog.com AlienVault OTX: https://otx.alienvault.com/indicator/domain/thymefoodblog.com URLhaus: https://urlhaus.abuse.ch/host/thymefoodblog.com/ ## ANALYST NARRATIVE ---------------------------------------------------------------- [Generated: 2026-07-17 09:20:18 UTC — narrative may predate facts above. Treat fields in TIMELINE / DETECTION EVIDENCE / INFRASTRUCTURE as authoritative if they differ from the prose below.] thymefoodblog.com - Generic Phishing Campaign Detected Analysis of thymefoodblog.com shows a newly registered domain (created 27 May 2026) hosted on IP 209.182.224.47 and using the registrar NAMECHEAP INC with authoritative name servers dns1.registrar-servers.com and dns2.registrar-servers.com. The domain is currently active and resolves to the same IPv4 address, indicating a single‑point hosting infrastructure typical of short‑lived phishing operations. No additional infrastructure such as CDN, secondary IPs, or sub‑domains has been observed. The classification as generic_phishing derives from threat intelligence tagging; no page content or brand impersonation details have been provided, so the exact lure remains unknown. Absence of public detection on VirusTotal does not imply benign intent, and the lack of further forensic artifacts limits confidence in attributing malicious use. Defenders should monitor DNS queries for the domain, block outbound connections to 209.182.224.47, and incorporate the domain into email and web filtering rules. Ongoing observation is advised to capture any payloads or phishing pages that may be deployed. Given the recent registration date, the domain may be part of a broader campaign that reuses similar infrastructure. Analysts should watch for patterns of registration using the same name servers or IP range, as these have been associated with other phishing sites in recent weeks. If future traffic exhibits credential‑stealing URLs or attachment downloads, the domain should be escalated to a higher threat tier. Until additional evidence is gathered, the domain remains under investigation. ## EVIDENCE HASHES ---------------------------------------------------------------- PhishDestroy Case ID: PD-20260717-367565 Favicon MD5: 3292e44ad66f1cc6284e8aee66f70300 TLS cert SHA-256: 87e0c7b8fcd030aaaa958fab20311c85c9f455a0a5482067db9a97aefce599d5 ## SCORING METHODOLOGY ---------------------------------------------------------------- Composite score is NOT derived from VirusTotal alone. PhishDestroy aggregates: - VirusTotal positive ratio - Public blocklist consensus (MetaMask, ScamSniffer, OpenPhish, PhishTank, URLhaus, CryptoFirewall, SEAL, Polkadot, Enkrypt, Phishunt, DiscordPhishing, PhishingDB) - Cloaking detection (HTTP 666 or rendering delta between bot and real visitor) - DNS-filter consensus (Quad9, CleanBrowsing, NextDNS, AdGuard, Cloudflare, etc.) - AlienVault OTX pulses + Cloudflare Radar + Google Safe Browsing - URLScan / URLQuery verdicts - Brand-impersonation heuristics (DOM analysis of forms, logos, wording) - Known phishing-kit fingerprinting (favicon hash, JS obfuscation signatures) - Wallet-drainer family classification (Angel, MS, Rainbow, Pink, Inferno, ...) - Free-TLS vs paid-cert ratio (throwaway infrastructure signal) - Registrar/hosting abuse history (this registrar's track record) - Human researcher sign-off (operator takedown team) A domain present in our database is ALREADY flagged. A low VT count by itself does NOT mean the domain is safe — new scam domains routinely show 0/95 VT for their first 7–30 days while actively draining wallets. Always cross-reference the composite score and the individual indicators above, not just VT. ## CORRECTIONS / APPEALS ---------------------------------------------------------------- Full HTML report: https://phishdestroy.io/domain/thymefoodblog.com/ JSON API: https://api.destroy.tools/v1/check?domain=thymefoodblog.com Appeal a flag: https://phishdestroy.io/appeals/ (responded to within 48 hours, FP rate <0.01%) Submit a report: https://t.me/PhishDestroy_bot About PhishDestroy: independent open-source threat-intelligence platform. Tracked: 188,947 domains (58,596 alive under monitoring, 128,729 confirmed takedowns/dead). Site: https://phishdestroy.io