zigbee-led.online
“Почти готово! Домен успешно привязан к хостингу”
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@reg.ru.
The latest stored availability evidence still shows the domain reachable; 37 hours 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.
zigbee-led.online — Último ativo conhecido (HTTP 200). Representação da marca: Unknown; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 1/89 (LevelBlue); URLScan capture; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 93/100. Registrador: Registrar of Domain Na….
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
Resumo das evidências
Assessment
Stored evidence for zigbee-led.online: VirusTotal recorded 1 detections among 89 scanners on 2026-09-19. That ratio reproduces the stored check in its original units and is not converted into another measure. SEAL appear as named external blocklist observations for zigbee-led.online. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 1 detections among 89 scanners in the stored snapshot dated 2026-09-19. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-19 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
SEAL are recorded as named external blocklist observations for zigbee-led.online in the snapshot dated 2026-09-19. The stored SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains zigbee-led.online as a publisher record. That PhishDestroy record is counted separately from the SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed zigbee-led.online on 2026-09-19. The SEAL blocklist snapshot is dated 2026-09-19 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-10. A URLScan reference was stored on 2026-09-19 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 31.31.197.26 as the observed address in this record. The registration date for zigbee-led.online is recorded as 2026-09-10. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The zigbee-led.online record states that VirusTotal recorded 1 detections among 89 scanners on 2026-09-19. SEAL remain named blocklist observations from the snapshot dated 2026-09-19. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 31.31.197.26. The supported conclusion is bounded to the exact stored observations for zigbee-led.online. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to zigbee-led.online during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain zigbee-led.online as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to zigbee-led.online. The stored record does not justify extending that rule to 31.31.197.26 or to other infrastructure records.
Forensic History & Detection Timeline
-
VirusTotal Detections Update Sep 19, 2026 · 11:37 UTCVirusTotal scanner detections updated from 0 to 1. Added scanner alerts: LevelBlue.
-
Threat First Observed Sep 19, 2026 · 10:02 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
31.31.197.26.
Pipeline de resposta a ameaças
Status da lista de bloqueios pública
Evasion analysis
Cloaking suspected: scanner and victim titles differ
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
nginx
Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
Captura armazenada · 3 sources
Inteligência de Domínios
Detalhes técnicosDNS, SANs do SSL, carimbos de data e hora
ICANN OVERSIGHT
Credenciamento e contexto RAA
Credenciamento e contexto 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.
Análise do VirusTotal
Análise de desempenho do site
Google PageSpeed Insights — mobile performance audit of zigbee-led.online · checked Sep 19, 2026
Evidências e relatórios externos
PD-20260919-E1F87D Recipient: abuse@reg.ru Abuse notice text as sent to the provider
Registrar: REG.RU (Russia) Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
Você foi afetado por este site?
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.
Notifique as autoridades locais
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Verificar qualquer domínio
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraDenunciar phishing
Envie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarFeed de ameaças em tempo real
Relatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMantenha-se informado, mantenha-se seguro
Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo