Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
网络安全情报 Registrar context
Registrar contextNameSilo
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.
PhishDestroy added authstep-booking664.com to its blocklist on 2026-10-22 after Google Safe Browsing marked the site for social engineering. The page fetched on that date returned HTTP 403 and no title was captured. The domain was first seen by PhishDestroy 72 days after its registration on 2026-08-11.
How the scam works
The detections point to a typical phishing or social‑engineering pattern where a deceptive page may solicit credentials or lure users to malicious links. No specific malicious payload or credential‑harvesting form was observed on the captured page.
Evidence
VirusTotal recorded 21 detections from 92 engines on 2026-10-22, with 18 classified as malicious and 3 as suspicious; vendors such as BitDefender, ESET and Forcepoint ThreatSeeker flagged it as phishing. Google Safe Browsing flagged the domain for social engineering on the same day. URLScan performed two scans: one returned a clean verdict, while a later scan on 2026-10-22 marked the URL malicious with a 97‑point ML score, and Cloudflare Radar labeled it as phishing and malware. OTX listed four pulses referencing the domain, and PhishDestroy’s internal blocklist marks it as malicious while external blocklists showed no hits at the time of checking.
Infrastructure
The domain was registered with NameSilo on 2026-08-11 and is hosted behind Cloudflare, resolving to IP 188.114.97.3 (ASN 13335, London, GB). TLS is provided by Google Trust Services, valid from 2026-09-10 to 2026-12-09, and the nameservers are ajay.ns.cloudflare.com and dawn.ns.cloudflare.com. DNSSEC is not enabled.
What to do
Visitors should avoid entering any credentials or clicking links on this domain and, if they have already submitted information, change associated passwords and monitor accounts for suspicious activity. Defenders should block authstep-booking664.com at network perimeters, log DNS queries for the domain, and keep threat‑intel feeds updated with its indicators. Continue to monitor the domain for any change in behavior, as the current 403 response does not guarantee future inactivity.
颁发者 Google Trust Services / WE1· stored validity ends in 48 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare
Edge-IP 声誉不属于此域。
域名服务器 2
ajay.ns.cloudflare.com
dawn.ns.cloudflare.com
Location describes the IP network.
TLS 证书
Issuer
Google Trust Services / WE1
Valid from
2026-09-10 13:42:57
Valid until
2026-12-09 14:41:29
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6d70648ce54ffe16191740b3f698374eda6613fc2ae86ebe89b9aaf45e6cbcdeCertificate names · 2 SANs
authstep-booking664.com
*.authstep-booking664.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.authstep-booking664.comDomain record
The original observation time is not recorded for these hostnames.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose 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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
PhishDestroy Investigation
