Lompat ke laporan keamanan
Dasbor Analitik
Keamanan domain dan intelijen ancaman
duplicate-disabled-211853.invalid favicon

duplicate-disabled-211853.invalid

“Persia Restaurant Oslo”

Registrar
NETIM
Resolved IP
104.21.52.206
Registered
17/04/2026
PhishDestroy assessment Kritis
Ketersediaan Konten tidak tersedia Konten tidak tersedia dalam observasi terbaru Teramati · HTTP probe
Sinyal risiko
Deteksi Total Virus: 2/91 Jenis penipuan: Credential Phishing
01/05/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 2. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
2 / 91
engine detections
Google Safe Browsing
No threat flag
Page captures
2
open gallery
Domain age
188 days
Ringkasan laporan

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

Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.

Source evidenceVirusTotal 2 / 91 7 sources

VirusTotal

2 / 91 engine detections

Buka laporan

PhishStats

checked — no match recorded

Pemblokiran DNS

14 diperiksa — tidak ada blokir

Google Safe Browsing

No threat flag

Buka laporan

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

Analysis

Kritis
VirusTotal
2 / 91
Page captures
2
Page captures Source results Registration record

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

Teramati: · Retrieved:

Uuid
019de076-4370-703f-9ae2-0e9bce27c467
Final url
https://www.persiarestaurant.no/meny/
Status
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"
]
Cookie
[
    "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

Teramati: · Retrieved:

Uuid
16b984da-83bc-431a-af02-806222527486
Final url
https://www.persiarestaurant.no/
Status
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

Tangkapan tersimpan · 2 captures

Primary capture 1 / 2
SumberPrimary capture
Recorded2026-04-30 23:16 UTC
StateStored capture
Position1 / 2
Open capture Wayback Unduh
Observed page title
Persia Restaurant Oslo
Sertifikat TLS
Diterbitkan oleh Let's Encrypt · stored validity ends in 76 days

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Registrar NETIM
Pendaftar ICANNICANN Lookup (RDAP) →
Pencarian WHOISICANN RDAP untuk duplicate-disabled-211853.invalid →
PendaftaranDibuat 17/04/2026 (188d)
Waktu hingga pertama kali tidak tersedia 9 days
Yang kami hitung Waktu yang berlalu sejak laporan penyalahgunaan pertama kali disimpan hingga pengamatan pertama bahwa konten tersebut tidak tersedia. Hal ini tidak dapat menentukan penyebabnya.
Isi setiap laporan Catatan laporan keluar yang disimpan dapat merujuk pada bukti yang tersedia pada saat itu, seperti keputusan vendor, data pendaftaran, detail hosting, klasifikasi, atau tangkapan layar. Halaman ini tidak menyimpulkan secara pasti muatan yang dikirimkan, penerimaan, pengakuan, atau tindakan oleh penerima.
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi01/05/2026
Submitted URLhttps://www.persiarestaurant.no/meny/
Favicon Hash
ICANN OVERSIGHT

Akreditasi dan konteks 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.

Akreditasi adalah kontrak, bukan cap jaminan keamanan. Verifikasi biaya ICANN Baca RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Tidak ada yang dikirim secara otomatis.

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

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 1

  • otto.ns.cloudflare.com

Location describes the IP network.

Sertifikat 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.

viewdns.info · 104.21.52.206rapiddns.io
Teknologi · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

2 / Vendor keamanan 91 menandai domain ini
View on VT
Last analyzed
Gridinsoft
SOCRadar

Bukti Terarsip

Wayback Machine Snapshot
Cuplikan sejarah tersedia untuk tinjauan bukti
View Archive
Analisis Performa Situs

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

    Dapat dijangkau→Tidak tersedia

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

Bukti & Laporan Eksternal

Analisis Keamanan
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery SSL Laboratorium Certificate hostname mismatch CF Radar Buka laporan WOT ScamAdviser Pemeriksa Daftar Hitam URLVoid Sucuri SiteCheck Observatorium MDN
OSINT & Intelijen
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Batu Hudson Sign-in search IntelX crt.sh Sertifikat WHOIS Wayback Archived
DNS & Jaringan
nslookup.io DNS bgp.tools ASN /Rute
SEO & Domain
SpyFu Moz DA/PA Ahrefs Tautan balik
Analisis Mendalam
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

3 evidence signal groups linked 0 stored notification records Konten tidak tersedia

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.

Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Bukan laporan penegakan hukum
Banding atas Nama Domain
Minta peninjauan jika Anda pemilik domain ini dan yakin cantumannya salah
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial. Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →

Laporkan kepada Pihak Berwenang di Daerah Anda

Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.

Direktori 97 negara

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

Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident

Rekomendasi & Saran bagi Para Korban

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

Apa yang harus saya lakukan segera?

Mendesak

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

  • Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
  • Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
  • Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut

Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?

Pedoman 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.
  • Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
  • Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
  • Semua URL & domain digunakan oleh penipu (termasuk duplicate-disabled-211853.invalid)
  • Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut

Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.

Ke mana saya harus melaporkan penipuan ini?

  • FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
  • Europol — Pelaporan kejahatan siber di Eropa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera

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?

  • Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
  • Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
  • Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi

Bagaimana cara saya melindungi diri di masa depan?

  • Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
  • Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
  • "Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak

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

Periksa Domain Apa Pun

Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik

Pindai Sekarang

Laporkan Phishing

Laporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas

Laporan

Pemberitahuan Ancaman Real-Time

Laporan phishing terbaru dan perubahan ketersediaan yang diamati

Pantau

Tetap Terinformasi, Tetap Aman

Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive

Pemberitahuan Ancaman Real-Time Ajukan Banding Terhadap Iklan Ini
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Sematkan Laporan Ini

Bagikan informasi ancaman ini di situs web atau blog Anda

embed.html 
<iframe
  src="https://phishdestroy.io/id/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>