Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
duplicate-disabled-211853.invalid favicon

duplicate-disabled-211853.invalid

“Persia Restaurant Oslo”

Registrador
NETIM
Resolved IP
104.21.52.206
Registered
17/04/2026
PhishDestroy assessment Crítico
Disponibilidad Contenido no disponible El contenido no estaba disponible en la última observación. Observado · HTTP probe
VirusTotal detecciones: 2/91 Tipo de estafa: Credential Phishing
01/05/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 2. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Resumen del informe

PhishDestroy identifies persiarestaurant.no as a credential theft phishing domain. SSL certificate analytics and IP 104.21.52.206 flagged. Check the full report

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 2 / 91 7 sources

VirusTotal

2 / 91 engine detections

Abrir informe

PhishStats

checked — no match recorded

Bloqueos de DNS

14 comprobado — sin bloqueos

Google Safe Browsing

No threat flag

Abrir informe

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
2 / 91
Page captures
2

PhishDestroy threat report

PhishDestroy identifies www.persiarestaurant.no as an active credential theft phishing domain under investigation. The site impersonates a legitimate restaurant brand, likely aiming to harvest user login credentials through fake reservation forms or payment portals. No drainer kit artifacts (e.g., wallet drainer scripts) are publicly documented, but the phishing mechanism is inferred from the domain’s behavior and structure. Brand impersonation is evident via a deceptive domain closely resembling a known restaurant chain, suggesting a social engineering tactic targeting users expecting to interact with a trusted service.

Technical indicators confirm this domain’s malicious nature. VirusTotal analysis shows 0/95 detections at the time of review, indicating evasion of current antivirus signatures. The domain resolves to IP 104.21.52.206 and is secured with a Let’s Encrypt SSL certificate, likely to appear legitimate. Registered on April 17, 2026, through a likely privacy-protected registrar, this domain is newly active and may have evaded blocklists. Google Safe Browsing (GSB) status is unflagged, and public blocklist reports (e.g., URLVoid, PhishTank) show zero current listings—highlighting its stealth and recent deployment.

The domain remains active with a high-risk status pending full forensic validation. Immediate actions include domain takedown advisories to hosting providers and registrars due to active phishing behavior. Users are advised to avoid interacting with the site, especially submitting credentials or payment data. Remaining risk is high due to the domain’s newness, SSL encryption, and lack of detection coverage—posing an imminent threat to unsuspecting visitors. Monitor for updates as threat intelligence evolves.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-04-30T22:15:52Z

Observado: · Retrieved:

Uuid
019de076-4370-703f-9ae2-0e9bce27c467
Final url
https://www.persiarestaurant.no/meny/
Estado
200
Ip
104.21.52.206
Contacted domains
[
    "m.media-amazon.com",
    "images-na.ssl-images-amazon.com",
    "fls-na.amazon.com",
    "unagi.amazon.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "44.215.115.167",
    "44.218.242.254",
    "104.16.79.73",
    "151.101.193.16",
    "104.21.52.206"
]
Asns
[
    "14618",
    "13335",
    "54113"
]
Countries
[
    "US"
]
Linked domains
[
    "www.amazon.com",
    "get.adobe.com",
    "pmaxwin138.firebaseapp.com"
]
Document hash
83ab6458bd6ce86be32f1ab0cae9970bad439acb311b2cdcee20bed248028290
Globals
[
    "aPageStart",
    "ue_t0",
    "ue_csm",
    "ue_hob",
    "ue_err_chan",
    "ue_id",
    "ue_url",
    "ue_navtiming",
    "ue_mid",
    "ue_sid",
    "ue_sn",
    "ue_furl",
    "ue_surl",
    "ue_fcsn",
    "ue_urt",
    "ue_rpl_ns",
    "ue_ddq",
    "ue_fpf",
    "ue_sbuimp",
    "ue_lpsi",
    "ue_lob",
    "ue_dsbl_cel",
    "ue_swi",
    "ue_viz",
    "ue_hoe",
    "ue_ihb",
    "ue",
    "ueLogError",
    "ue_err",
    "ueinit",
    "uei",
    "ueh",
    "ues",
    "uet",
    "uex",
    "onLd",
    "onLdEnd",
    "onUl",
    "onstop",
    "_pSetI"
]
Cookies
[
    "csm-hit"
]
Storage keys
[
    "csm-hit",
    "csa.cajun.bn65pu-8vwt4w-i0m7hn-rvlkae"
]
Tls
{
    "san": [
        "*.persiarestaurant.no",
        "persiarestaurant.no"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "E8",
    "subject": "persiarestaurant.no",
    "protocol": "QUIC",
    "valid_to": "2026-07-16T14:26:23Z",
    "valid_from": "2026-04-17T14:26:24Z"
}
Domain age days
1476
Apex age days
1773
Tls age days
13
Tls valid days
89
Requests
143
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -44,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-04-30T22:16:53Z

Observado: · Retrieved:

Uuid
16b984da-83bc-431a-af02-806222527486
Final url
https://www.persiarestaurant.no/
Estado
200
History
[
    {
        "url": "https://www.persiarestaurant.no/",
        "status": 200
    }
]
DOM structure hash
51ea556348408e2786c9e9cb36ab803f8148f19a640f5571103b8adc8e62854e
Document hash
7585052d17548e3e81a097f153f8d16a2ee8808aa57e04b686cdc09ab5aa8d64
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "www.persiarestaurant.no",
        "type": "A",
        "value": "172.67.203.167"
    },
    {
        "name": "www.persiarestaurant.no",
        "type": "A",
        "value": "104.21.52.206"
    },
    {
        "name": "www.persiarestaurant.no",
        "type": "AAAA",
        "value": "2606:4700:3032::6815:34ce"
    },
    {
        "name": "www.persiarestaurant.no",
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:cba7"
    }
]
Dnssec valid
false
Ip
172.67.203.167
Registration record
{
    "created": "2026-04-17T00:00:00Z",
    "updated": "2026-04-17T00:00:00Z"
}
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 2 captures

Observed page title
Persia Restaurant Oslo
Certificado TLS
Emitido por Let's Encrypt · stored validity ends in 76 days

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Registrador NETIM
RegistroCreado 17/04/2026 (188d)
Tiempo hasta la primera indisponibilidad 9 days
Qué contabilizamos Tiempo transcurrido desde el primer informe de abuso almacenado hasta la primera observación de que el contenido no estaba disponible. Esto no establece la causa.
Qué contiene cada informe Los registros de informes salientes almacenados pueden hacer referencia a evidencia disponible en ese momento, como veredictos de proveedores, datos de registro, detalles de alojamiento, clasificaciones o capturas de pantalla. Esta página no infiere la carga útil entregada, el recibo, el acuse de recibo o la acción exacta por parte de un destinatario.
Detalles técnicosProvenance & timestamps
Primera detección01/05/2026
Submitted URLhttps://www.persiarestaurant.no/meny/
Favicon Hash
ICANN OVERSIGHT

Acreditación y 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.

Accountability draft No se envía nada automáticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.52.206
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

La reputación de Edge-IP no se atribuye a este dominio.

Servidores de nombres 1

  • otto.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt
Valid from
2026-04-17 14:26:24
Valid until
2026-07-16 14:26:23
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-05-01 02:00:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint56f7b536e8c3a414752495e7e22ac9d7d0a1385a488356fbb33fc545da475358
Certificate names · 1 SANs
  • persiarestaurant.no

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Tecnologías · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

2 / Los proveedores de seguridad de 91 marcaron este dominio
View on VT
Last analyzed
Gridinsoft
SOCRadar

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of duplicate-disabled-211853.invalid · checked May 1, 2026

78
Needs Work
Performance
FCP
3.01s
First Contentful Paint
LCP
3.75s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
6.5s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

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='duplicate-disabled-211853.invalid', port=80): Max retries exceeded with url: / (Caused by

duplicate-disabled-211853.invalid
Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Accesible→No disponible

Recorded activity

3 entries
  1. VirusTotal

    2/91 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Added to PhishDestroy

    duplicate-disabled-211853.invalid

    View source

Datos y informes externos

Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

3 evidence signal groups linked 0 stored notification records Contenido no disponible

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.

Official reporting routes

¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del FBI

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.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos duplicate-disabled-211853.invalid)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/duplicate-disabled-211853.invalid"
  title="PhishDestroy threat report for duplicate-disabled-211853.invalid"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>