VirusTotal
2 / 91 engine detections
レポートを開く“Persia Restaurant Oslo”
PhishDestroy identifies persiarestaurant.no as a credential theft phishing domain. SSL certificate analytics and IP 104.21.52.206 flagged. Check the full report
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 91 engine detections
レポートを開くchecked — no match recorded
no community references
レポートを開くprovider verdict: clean
レポートを開く14 確認済み — ブロックなし
No threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
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.
Stored page, network and scanner observations, grouped by source and observation time.
観測された: · Retrieved:
| Uuid | 019de076-4370-703f-9ae2-0e9bce27c467 |
|---|---|
| Final url | https://www.persiarestaurant.no/meny/ |
| ステータス | 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"
] |
| クッキー | [
"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"
} |
観測された: · Retrieved:
| Uuid | 16b984da-83bc-431a-af02-806222527486 |
|---|---|
| Final url | https://www.persiarestaurant.no/ |
| ステータス | 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"
} |
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.
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.
Edge-IP の評判はこのドメインに起因しません。
otto.ns.cloudflare.comLocation describes the IP network.
56f7b536e8c3a414752495e7e22ac9d7d0a1385a488356fbb33fc545da475358persiarestaurant.noSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-211853.invalid · checked May 1, 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.
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
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
2/91 engine detections
View sourceNo threat flag
View sourceduplicate-disabled-211853.invalid
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
duplicate-disabled-211853.invalid)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.