Analysis of towns.community indicates a phishing domain targeting American Express customers, despite displaying a Bank of America-themed page title. The domain was registered on August 6, 2025, through Web Commerce Communications Limited (WebNic.cc) and resolves to IP 179.43.188.122, hosted on AS51852 (Private Layer INC) in Switzerland. The SSL certificate is issued by GlobalSign, a common feature in phishing infrastructure to lend superficial legitimacy. The site's page title, 'Bank of America | Online Banking | Forgot User ID & Password,' suggests an attempt to deceive users into entering credentials, though the mismatch with the declared brand target (American Express) may indicate a broader or repurposed phishing kit. Security vendors have flagged this domain as malicious, with 8 of 93 engines on VirusTotal detecting it as phishing-related.
It appears on two security blocklists and is actively blocked by PhishDestroy and ScamSniffer. AlienVault OTX includes the domain in one threat intelligence pulse, further corroborating its association with malicious activity. Gridinsoft assigns a trust score of 0/100, reinforcing its high-risk classification. As of July 24, 2026, the domain is offline, though its prior infrastructure and detection history warrant continued monitoring. Defenders should treat this domain as confirmed phishing infrastructure, particularly for financial credential theft.
Network-level blocking of the IP (179.43.188.122) and domain is recommended. Given the registrar and hosting provider, similar domains may emerge from the same threat actor. Security teams should review logs for prior connections to this domain or IP, particularly in contexts involving financial services or credential submission. No evidence links this domain to a specific phishing kit or campaign beyond the banking phishing classification provided.
DOM Analysisanalyzed 2026年3月24日score 75/1006 brand signals
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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:14:06 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:18:13 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:18:13 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:34 UTC · precision 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.
Last analyzed Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
ソフォス
Webroot
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low
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='towns.community', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
towns.community
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.
(MY)
