Notification and current-status evidence
The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 5 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
slon-1[.]net
“slon1.cc”
Résumé des preuves
slon-1.net has been observed as an active phishing infrastructure since its registration on 27 February 2026. The domain is delegated to Cloudflare’s authoritative name servers dante.ns.cloudflare.com and mckinley.ns.cloudflare.com, indicating the use of Cloudflare’s DNS and CDN services. The registration was performed through NiceNIC International Group Co., Limited, and the domain points to the IP address 188.114.97.3, which belongs to Cloudflare’s AS13335 network located in the United States.
The web service returns an HTTP 301 redirect and serves a TLS certificate issued by Let’s Encrypt (subject identifier E8). The page title presented to browsers is “slon1.cc”, a mismatch that suggests intentional obfuscation or re‑branding of the landing page. Underlying technologies identified include Cloudflare Browser Insights and HTTP/3, confirming that traffic is being proxied through Cloudflare’s edge network. No additional hosting details are exposed beyond the Cloudflare front‑end.
Reputation signals corroborate the malicious intent. VirusTotal scans flagged the domain by 4 of 95 security vendors, and the domain appears on a single public blocklist. Gridinsoft assigns a trust score of 0 out of 100, and PhishDestroy has already blocked the domain. The limited number of detections may reflect the short operational window, but the convergence of low trust scoring, blocklist presence, and redirect behaviour is consistent with a high‑risk phishing campaign.
Defenders should add slon-1.net to network deny lists and configure DNS filtering to return NXDOMAIN or sinkhole responses. Monitoring for additional domains that resolve to the same Cloudflare IP range is advisable, as threat actors often spin up new hostnames on shared infrastructure. Incident response teams should also examine any compromised credentials that may have been harvested through the site, and users should be warned to avoid clicking links that reference the domain or its “slon1.cc” title.
Instantané des preuves transmises
- Envoyé
- Entrées du registre
- 1
- ID du dossier
PD-20260227-54C178- Titre de la page capturée
- slon1.cc
- Artefact PDF
- Preuve PDF
Texte intégral des preuves
Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown
Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
Data Coverage
Renseignements sur la sécurité réseau
Processus de réponse aux menaces Pipeline
Couverture des listes de blocage
10 sources externes surveillées · instantané du 12/08/2026
10 sources externes surveillées Aucune correspondance
Chronologie de détection
-
VirusTotal
0 → 2
-
VirusTotal
0 → 2
-
Cloudflare Radar
Analyse Cloudflare Radar enregistrée · Ouvrir l’analyse
-
VirusTotal
3 → 4
-
État du domaine
Accessible → Inaccessible
-
Cloudflare Radar
Analyse Cloudflare Radar enregistrée · Ouvrir l’analyse
Capture enregistrée
Informations sur les domaines
Détails techniquesDNS, noms TLS et horodatages
ICANN OVERSIGHT
Contexte de l’accréditation et du RAA
Contexte de l’accréditation et du 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.
Analyse VirusTotal
Ce site vous a-t-il affecté ?
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Signalez-le à vos autorités locales
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Vérifier n'importe quel domaine
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignaler une tentative d'hameçonnage
Signalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerFlux d'alertes en temps réel
Rapports de phishing récents et changements de disponibilité observés
SurveillerRestez informés, restez en sécurité
Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif