VirusTotal
9 / 91 engine detections
Abrir relatório“Not Acceptable!”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@bluehost.com.
The latest stored availability evidence still shows the domain reachable; 21 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Imitação de Spectrum: justina.com.do — Último ativo conhecido (HTTP 200). Resumo das evidências: VirusTotal 9/91 (alphaMountain.ai, CRDF, Forcepoint…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
9 / 91 engine detections
Abrir relatório2 det.
Abrir relatórioThreat flag recorded
Abrir relatórioMalicioso
Abrir relatório5 community references
Abrir relatórioprovider verdict: clean
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
justina.com.do is a phishing page that impersonates Spectrum, the US internet, cable TV and email provider, and targets its subscribers. PhishDestroy first flagged it on 2026-09-29. As of 2026-10-19 the site was still online and serving content. The page title reads "Not Acceptable!", which looks like a server error rather than a branded login, but scanners still detected Spectrum branding on the page we classified as impersonation.
Spectrum phishing usually starts with an email or text claiming a billing problem, a suspended account or a mailbox that needs verifying. The link leads to a page styled like Spectrum's sign-in. Anything typed there goes to the operators, including usernames, passwords, and sometimes payment card or personal details. A stolen Spectrum login can expose the victim's email inbox, which in turn opens password resets for banking, crypto exchanges and other accounts.
Nine of 91 VirusTotal engines flag the domain as of 2026-10-03, among them Google Safe Browsing, Fortinet, Sophos, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, Gridinsoft and SOCRadar. That is a modest count, but it comes from several vendors working independently. Google Safe Browsing lists it under SOCIAL_ENGINEERING, so Chrome, Firefox and Safari users should see a warning page. urlscan.io returned a malicious verdict and identified Spectrum as the imitated brand. The domain also appears in five AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2013-08-07 through NIC .DO, the Dominican Republic registry. That is about thirteen years before PhishDestroy detected it, so reputation checks based on domain age would not catch it. It resolves to 162.241.27.245 on the Unified Layer shared-hosting network, geolocated to India. The Let's Encrypt certificate makes the padlock appear in the browser, but the padlock only means the connection is encrypted and says nothing about whether the site is legitimate.
If you entered your Spectrum credentials on this page, change your Spectrum password right away from Spectrum's official app or website. Then do the same for any other account that used the same password. Turn on two-step verification and check your Spectrum email for forwarding rules or recovery addresses you did not set up. If you entered card details, contact your bank to block the card and dispute any charges. Security teams should block the domain and its IP at the mail gateway and web proxy, and search logs for users who visited it.
rns3.webhostbox.netrns4.webhostbox.netjustina.com.dopriority 0Location describes the IP network.
e7489033b21c72455130ff29f9ca94231fc5f932ffa6ab515ce64d660c329ae8Saved 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.
autodiscover.justina.com.doDomain recordcolinasdavidantonio.justina.com.doDomain recordcpanel.justina.com.doDomain recordcpcalendars.justina.com.doDomain recordcpcontacts.justina.com.doDomain recordemail.correo.justina.com.doDomain recordmail.justina.com.doDomain recordwebdisk.justina.com.doDomain recordwebmail.justina.com.doDomain recordwww.justina.com.doDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of justina.com.do · checked Sep 29, 2026
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.
alive_content: raw=ok; http=200; via=https_proxy; server=Apache
justina.com.do
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
No flag recorded→Flag recorded
Acessível
Threat flag recorded
View source5 community references
View source9/91 engine detections
View sourcePD-20260929-BBF73F
Page captured
View sourcejustina.com.do
View sourcePD-20260929-BBF73F Recipient: abuse@bluehost.com Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
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 ↗
justina.com.do)Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.
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
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um 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.