VirusTotal
12 / 89 engine detections
Apri il rapporto“Bank of America | Online Banking | Forgot User ID & Password”
Phishing di credenziali: towns.community — Contenuto non disponibile. Riepilogo delle prove: VirusTotal 12/89 (alphaMountain.ai, BitDefender, Chong Lua Dao…
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
12 / 89 engine detections
Apri il rapportoMalevolo
Apri il rapportochecked — no detections recorded
Apri il rapporto1 community reference
Apri il rapportoNo threat flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
Last checked
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.
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.
Location describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
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
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
12/89 engine detections
View sourceNo threat flag
View source1 community references
View sourcetowns.community
View sourceSegnalato da 1 membro della comunità; prima osservazione il 15/08/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
towns.community)Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaSegnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraControlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo
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.