This domain is currently under investigation for credential harvesting targeting short-term rental platforms, specifically impersonating Airbnb login portals. Analysis indicates a generic phishing threat with potential for financial fraud through stolen account access or payment redirection. Infrastructure analysis reveals the domain bnbsmart.network was registered on May 11, 2026, through NameCheap, Inc. and resolves to IP address 216.150.1.1, hosted on Amazon.com, Inc. infrastructure (AS16509) in the United States. The domain lacks SSL encryption, creating an immediate risk for unencrypted credential transmission. Detection metrics show 0/95 detections on VirusTotal, suggesting either recent deployment or effective evasion techniques. The domain appears on one security blocklist (PhishDestroy) and remains actively resolving. Organizations and individuals should implement the following mitigation measures: (1) Block the domain and IP 216.150.1.1 at firewall and DNS filtering levels; (2) Monitor for credential reuse attempts from any accounts that may have interacted with this domain; (3) Deploy email filtering rules to quarantine messages containing this domain or similar patterns (e.g., 'bnb' + 'smart'); (4) Conduct user awareness training focused on identifying unencrypted login pages (HTTP vs HTTPS) and verifying domain authenticity before entering credentials; (5) Implement multi-factor authentication on all short-term rental platform accounts to mitigate credential theft impact. The anomalous creation date (2026) suggests potential domain squatting or registry system manipulation that warrants further investigation.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
IoC Extractionscanned 2026年8月1日1 wallet · 0 Telegram IoC
Submitted URLhttps://bnbsmart.network/
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:08:03 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-25 10:19:29 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-25 10:19:29 UTC → 2026-09-30 16:14:55 UTC · 2,333.92hmidpoint estimate ≈ 2026-08-13 01:17:12 UTC · precision very low · basis bounded
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bnbsmart.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
bnbsmart.network
保存済みの結果
到達不能
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
詐欺による金銭の返還を装った詐欺 — 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.
