セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
vlodrome.finance のファビコン

vlodrome.finance

要点

vlodrome.finance:Velodromeなりすまし。PhishDestroy が 2026-10-19 に検出しました。リスク:クリティカル(100/100)。レジストラ:NiceNIC。ステータス:最後に確認されたアクティブな状態。ホスティング:Cloudflare, Inc。VirusTotal:11/92 のエンジンが検出。Spamhaus DBL に掲載。認証情報を入力したり、ウォレットを接続したりしないでください。

レジストラ
NiceNIC
Resolved IP
188.114.96.3
Registered
2026年10月13日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 11/92 Spamhaus DBL: DBL_SPAM 自動ブランドラベル:Velodrome 若いドメイン: 11 日経過
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
ページキャプチャ
ギャラリーを開く
ドメイン年齢
送信済み報告
No sent record
OTX: 4 refs 2026年10月19日 CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 11。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
レポート概要

Velodromeなりすまし: vlodrome.finance — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 11/92 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, Forcepoint…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Analysis

Domain summary

vlodrome.finance:Velodromeなりすまし。PhishDestroy が 2026-10-19 に検出しました。リスク:クリティカル(100/100)。レジストラ:NiceNIC。ステータス:最後に確認されたアクティブな状態。ホスティング:Cloudflare, Inc。VirusTotal:11/92 のエンジンが検出。Spamhaus DBL に掲載。認証情報を入力したり、ウォレットを接続したりしないでください。

クリティカル
VirusTotal
11 / 92
OTX
4 community refs
ページキャプチャ
5

PhishDestroy threat report

Overview

vlodrome.finance is a domain flagged by PhishDestroy as suspicious. It was first seen by PhishDestroy on 2026-10-19 and remains classified as a suspicious domain. The site is currently unreachable but was active at the time of last check on 2026-10-19.

How the scam works

Sites like this often mimic legitimate financial or cryptocurrency platforms to deceive visitors into connecting wallets or entering credentials. While the exact mechanism is not confirmed, such domains typically aim to steal funds, credentials, or approvals from users who interact with them. The risk includes unauthorized transactions, wallet draining, or data theft if users engage with the site.

Evidence

The domain shows 11 detections out of 92 engines on VirusTotal, flagged by vendors including alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, and Kaspersky. It is listed on the PhishDestroy blocklist and appears in 4 OTX pulses.

Infrastructure

The domain was registered on 2026-10-13 with NICENIC INTERNATIONAL GROUP CO., LIMITED. It is hosted on IP 188.114.96.3 and uses a TLS certificate issued by Let's Encrypt / YE1.

What to do

If you visited this site, do not connect your wallet or enter any credentials. Revoke any suspicious approvals in your wallet settings. Report the domain to your wallet provider or security team. For defenders, block the domain and monitor for related infrastructure. Disable access to the hosting IP if possible.

ソース別の証拠VirusTotal 11 / 92 · OTX 4 references 8 sources

VirusTotal

11 / 92 engine detections · stored summary

レポートを開く
VirusTotalOriginal source recordRetrieved: 12 fields

観測された: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Lionic": "malicious",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "malicious",
    "Kaspersky": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Bfore.Ai PreCrime": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
}
作成日
2022-07-28T00:00:00Z
Updated
2022-07-28T00:00:00Z
初回確認
2025-06-24T03:12:23Z
DNS レコード
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::6815:2d21"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "elma.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:d05b"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "elma.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.45.33"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "valentin.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.208.91"
    }
]
Dns at
2026-10-18T21:18:47Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.vlodrome.finance",
        "vlodrome.finance"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "56ebc09f6ede5a3a4942a626e19d06e9aec",
    "sha256": "f27eaae8e2fc2d5c82dfe7a2b43f1c464bb3551446e2e4f3f8ba61743edca66d",
    "subject": "vlodrome.finance",
    "valid_to": "2027-01-14T18:02:50Z",
    "valid_from": "2026-10-16T18:02:51Z"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-13T16:00:00Z",
        "registration": "2026-10-13T16:00:00Z",
        "registrar expiration": "2027-10-13T16:00:00Z",
        "last update of RDAP database": "2026-10-13T16:00:00Z"
    },
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "registrar_iana_id": "3765"
}
Separate source record · 12 malicious + 0 suspicious / 92 · 2026-10-18 21:07:42 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-18T21:07:42Z
fetched_at
2026-10-20T18:06:51Z
stats
{"timeout":0,"harmless":48,"malicious":12,"suspicious":0,"undetected":32}

Cloudflare Radar

Phishing

レポートを開く
Cloudflare RadarOriginal source recordRetrieved: 14 fields

観測された: · Retrieved:

Uuid
c994c633-25fc-4702-aacb-6dea5d7eedb0
Final url
https://velodrome.finance-eka.eu.cc/
ステータス
200
リダイレクト
off-domain
History
[
    {
        "url": "https://vlodrome.finance/",
        "status": 301
    },
    {
        "url": "https://velodrome.finance-eka.eu.cc/",
        "status": 302
    },
    {
        "url": "https://velodrome.finance-eka.eu.cc/",
        "status": 200
    }
]
DOM structure hash
ce804b15be786b463588ff6fda5fa5cb425cef3795ff8da0509d9df9c026bb0b
Document hash
b138ff2cf923778dbd5d65784b5f324a7d9d4e3293716ef4884c6112afc3a633
Phishing v2
[
    "phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS レコード
[
    {
        "name": "velodrome.finance-eka.eu.cc",
        "type": "A",
        "value": "104.21.7.222"
    },
    {
        "name": "velodrome.finance-eka.eu.cc",
        "type": "A",
        "value": "172.67.156.125"
    },
    {
        "name": "velodrome.finance-eka.eu.cc",
        "type": "AAAA",
        "value": "2606:4700:3035::6815:7de"
    },
    {
        "name": "velodrome.finance-eka.eu.cc",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:9c7d"
    }
]
DNSSEC 有効
false
Ip
104.21.7.222
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
登録記録
{
    "registrar": "SevenX LLC",
    "created": "1997-10-13T04:00:00Z",
    "updated": "2026-08-31T10:38:55Z",
    "expires": "2032-03-26T04:00:00Z",
    "nameservers": [
        "a.rsp-dns.com",
        "b.rsp-dns.com"
    ]
}

Spamhaus DBL

DBL_SPAM

URLScan

悪意あり

レポートを開く
URLScanOriginal source recordRetrieved: 21 fields

観測された: · Retrieved:

Uuid
01a152da-1406-7213-b20c-3c467bc8dd69
Final url
https://velodrome.finance-eka.eu.cc/
ステータス
200
リダイレクト
off-domain
Redirects
[
    {
        "to": "https://velodrome.finance-eka.eu.cc/",
        "from": "https://vlodrome.finance/",
        "status": 301
    },
    {
        "to": "https://velodrome.finance-eka.eu.cc/",
        "from": "https://velodrome.finance-eka.eu.cc/",
        "status": 302
    }
]
Ip
104.21.7.222
Contacted domains
[
    "static.cloudflareinsights.com",
    "vlodrome.finance"
]
Contacted IP addresses
[
    "104.16.79.73",
    "104.21.7.222",
    "172.67.208.91"
]
Asns
[
    "13335"
]
Linked domains
[
    "velodrome.finance-eka.eu.cc",
    "www.cloudflare.com"
]
Document hash
64c4645be3e6261f1de7d5fab708d1be033fbb87b3abde53991f687c002408fd
Globals
[
    "postClick",
    "__cfBeacon"
]
クッキー
[
    "_sv",
    "_sr"
]
Tls
{
    "san": [
        "*.finance-eka.eu.cc",
        "finance-eka.eu.cc"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "finance-eka.eu.cc",
    "protocol": "QUIC",
    "valid_to": "2027-01-14T18:53:53Z",
    "valid_from": "2026-10-16T18:53:54Z"
}
ドメイン年齢(日数)
2
Apex age days
2
Tls age days
2
TLS 有効日数
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 74,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "genericcrypto"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Generic Crypto"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-10-20T03:30:13Z

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a152da-1406-7213-b20c-3c467bc8dd69
score
100
malicious
true
result_at
2026-10-20T03:30:13Z
enriched_at
2026-10-19T08:10:34Z
source_timestamps
{"urlscan_result_at":"2026-10-20 05:30:13","urlscan_enriched_at":"2026-10-19 10:10:34"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy DOM

100 / 100 · heuristic score · 1 brand references · 1 classifications

レポートを開く
Separate monitor score · 10 / 100 · 2026-10-19T10:20:06Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-19T10:20:06Z
source_timestamp
2026-10-19 12:20:06
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

レポートを開く
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
vlodrome.finance — Suspicious Domain
ai_description
vlodrome.finance is a newly registered site on the PhishDestroy blocklist that mimics a financial platform and shows multiple security vendor detections.
ai_generated_at
2026-10-19T07:54:40Z
ai_generated_by
threat-mistral
interpretation
Narrative generation metadata, separate from provider observation dates.

結果は各ソースの収集時点のものです。検出ゼロは安全性を保証しません。OTX の参照情報はコミュニティによる公開情報です。

収集したソースの詳細

保存されたページ、ネットワーク、スキャナーの観測結果を、ソースと観測時刻ごとにまとめています。

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields
Mail configuration
{
    "spf_lookups": 0
}
CAA レコード
{
    "domain": "vlodrome.finance"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-07-14T20:37:06Z",
    "first": "2025-07-14T20:37:06Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 411
}
ページタイトルとメタデータ
{
    "title": "On slow tools — Haven Kit"
}
Trackers
{
    "requests": 3
}
フォームと混合コンテンツ
{
    "third_party_scripts": 0
}
ステータス
{
    "up": true,
    "code": 301,
    "timings": {
        "dns": 18,
        "tls": 42,
        "wait": 575,
        "connect": 962,
        "download": 0
    },
    "response_ms": 1597
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 2953,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.32.154",
            "host": "elma.ns.cloudflare.com"
        },
        {
            "ip": "172.64.35.206",
            "host": "valentin.ns.cloudflare.com"
        }
    ],
    "zone": "vlodrome.finance"
}
クッキー
{
    "cookies": [
        {
            "name": "_sv",
            "http_only": true
        },
        {
            "name": "_sr"
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3121::9",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "vlodrome.finance"
}
DNS レコード
{
    "A": [
        "188.114.97.9",
        "188.114.96.9"
    ],
    "NS": [
        "elma.ns.cloudflare.com",
        "valentin.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"elma.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417881809, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::9",
        "2a06:98c1:3121::9"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::9",
    "family": 6
}
Redirects
{
    "chain": [
        "https://vlodrome.finance",
        "https://velodrome.finance-eka.eu.cc",
        "https://velodrome.finance-eka.eu.cc/"
    ],
    "count": 2
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "HTTP/3"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8"
    }
}
ネットワークセキュリティインテリジェンス レジストラの背景情報
CF Cloudflare Radar Verdict 悪意あり
Phishing
レジストラの背景情報 NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

vlodrome.finance についての質問

vlodrome.finance は正規のサイトですか?

いいえ。PhishDestroy は vlodrome.finance を「Velodromeなりすまし」に分類しています(リスク:クリティカル、100/100)。初回検出は 2026-10-19 です。VirusTotal:11/92 のエンジンが検出。Spamhaus DBL に掲載。安全でないサイトとして扱ってください。

vlodrome.finance にウォレットを接続しても安全ですか?

いいえ。vlodrome.finance でウォレットを接続したり、メッセージに署名したり、トークンを承認したりしないでください。フィッシングサイトは運営者があなたの資産を移動できる承認(approve、setApprovalForAll、Permit2)を求め、確定した取引は取り消せません。

vlodrome.finance を利用してしまった場合はどうすればよいですか?

そこで入力したパスワードをすべて変更し、二要素認証を有効にしてください。ウォレットを接続したり署名したりした場合は、承認を取り消し、残りの資金を新しいウォレットに移してください。シードフレーズは決して共有しないでください。手順ガイド:緊急対応ガイド。

関連情報

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list ソースを表示

保存済みキャプチャ · 5 件のキャプチャ

All capture links and hashes (5)
Automated brand references
Velodrome
TLS証明書
発行者 Let's Encrypt / YE1 · 保存された有効期限まで残り 81 日

ドメインの詳細

ドメイン
URLScan verdict 悪意あり score 100 Phishing report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
OTX tags 2026-10activeall-domainsblocklistcontentcryptoドメインdrainerfraudlivemonthlyphishdestroyphishingscam
レジストラ NiceNIC RU(RU) PhishDestroy Investigation
不正利用連絡先abuse@nicenic.net
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年10月13日 (11d · Very New!) — Expires 2027年10月13日
HTTPステータス301 Moved Permanently
技術詳細Provenance & timestamps
初確認2026年10月19日
DOM Analysisanalyzed 2026年10月19日score 100/1001 brand signal
Submitted URLhttps://vlodrome.finance/
Favicon Hash
ICANN OVERSIGHT

認定と RAA の背景

レジストラの認定と DNS 不正利用対策の義務

この gTLD では、上記のレジストラは ICANN の認定契約に基づいて運営されています。以下のリンクから、公式の料金表と現行の DNS 不正利用に関するコンプライアンスガイダンスを確認できます。

認定は契約であり、安全性の認証ではありません。

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 自動送信は一切行われません。

ネットワーク & 証明書

保存済みの技術的証拠

ネットワーク & DNS

Shared CDN edge
Resolved IP
188.114.96.3
ネットワーク ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP の評判はこのドメインに起因しません。

ネームサーバー 2

  • elma.ns.cloudflare.com
  • valentin.ns.cloudflare.com

所在地は IP ネットワークの位置を示します。

TLS証明書

Issuer
Let's Encrypt / YE1
有効期間の開始
2026-10-16 18:02:51
有効期間の終了
2027-01-14 18:02:50
Validity
保存された有効期間内
Collection time
2026-10-19 07:02:04 UTC
収集元
PhishDestroy collector
証明書のフィンガープリントf27eaae8e2fc2d5c82dfe7a2b43f1c464bb3551446e2e4f3f8ba61743edca66d

保存された証明書のメタデータです。タイムゾーンのない証明書の日付は、保存時の値のまま表示しています。通信の暗号化は、サイトが信頼できることを示すものではありません。

Latest Classified Outcome 2026-10-25 04:03:20 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 04:03:20 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-25 04:03:20 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains3

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • t299r7.vlodrome.financeDomain record
  • webmail.vlodrome.financeDomain record
  • www.vlodrome.financeDomain record

The original observation time is not recorded for these hostnames.

使用技術 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

11 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
VT で表示
最終分析 First positive detection 以前の保存スナップショット: 11 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
カスペルスキー
Lionic
ソフォス
Webroot
サイトパフォーマンス分析

Google PageSpeed Insights — 次のドメインのモバイルパフォーマンス監査: vlodrome.finance · checked Oct 19, 2026

97
Good
Performance
FCP
1.82 s
First Contentful Paint
LCP
1.83 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.48 s
Speed Index
データ提供: Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
保存済みキャプチャの証拠 1 snapshot

ローカル収集パイプラインが保持している、タイムスタンプ付きのレスポンスメタデータです。以下の各値は、表示されているアーカイブ時刻のものです。

Archived HTTP response HTTP 200
Requested URL: https://vlodrome.finance/
Final URL: https://velodrome.finance-eka.eu.cc/
Just a moment...
対応
HTTP 200
HTML body
67.1 KB
Compressed
13.4 KB
Links
0 internal · 2 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS:観測されず DNSSEC:観測されず WAF / firewall: observed クローキングフラグ:観測されず
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4cdbceffc3c3dd6-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 19 Oct 2026 06:31:07 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OreZWy3lxGT7vpUcF2jSyg74MUDelFWkqU0AAGNxTbxnvMIjJxYX6C25oXJeAh6UCAKHClt3c5YycVjtAOiDlHSqAydrR%2BTjbQLhSccgP4M1kkDEFI5S%2Bb2mZwwqrBFAueR%2Fq8fwV
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Cookie,Accept-Encoding

コレクターが保持している値です。長い値は収集時に短縮されている場合があります。

Registration & observation details2

Availability observations

最後にアクセス可能だった観測
Estimate basis
Currently reachable

推定時刻は観測期間の幅を示すものです。レジストラによる措置や、サイトがアクセス不能になった正確な時点を証明するものではありません。

保存済みの観測履歴6

モニターと各ソースのコレクターが保持している、日付付きの変更履歴です。新しい観測から順に表示されます。ソースの状態はテイクダウンの証明ではありません。

  1. 可用性モニター · 記録された状態

    不明→redirected

    http_redirect

  2. 可用性モニター · 記録された状態

    不明→redirected

    http_redirect

  3. 可用性モニター · 記録された状態

    不明→redirected

    http_redirect

  4. 可用性モニター · 記録された状態

    不明→redirected

    http_redirect

  5. 可用性モニター · 記録された状態

    不明→redirected

    http_redirect

Earlier observations 1
  1. Domain monitor · First collection record

    到達可能

All retained availability observations31

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:03:20.000000
    証拠の SHA-256
    cf98697bfb29909b9df6596639058a5b8151d3c8d7f7f8f7effcf7bfe2b25331
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 05:03:20
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:03:20.000000
    証拠の SHA-256
    cf98697bfb29909b9df6596639058a5b8151d3c8d7f7f8f7effcf7bfe2b25331
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 05:03:20
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 13:05:20.000000
    証拠の SHA-256
    0cbf4f9a82af13568c21eb1aa780b1aa0f1a74fb1ed391602c55419072c9746d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 13:05:20
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 13:05:20.000000
    証拠の SHA-256
    0cbf4f9a82af13568c21eb1aa780b1aa0f1a74fb1ed391602c55419072c9746d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 13:05:20
    Evidence reason
    redirect
  5. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 04:42:33.000000
    証拠の SHA-256
    0d3ce7debceaa9c8ad91b8a20f70422092052447530b7b051616de73d9f661b2
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 04:42:33
    Evidence reason
    redirect
  6. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 04:42:33.000000
    証拠の SHA-256
    0d3ce7debceaa9c8ad91b8a20f70422092052447530b7b051616de73d9f661b2
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 04:42:33
    Evidence reason
    redirect
  7. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:06:54.000000
    証拠の SHA-256
    ec71e8bfc1d0d803e8de08ab87c1d3692fd9941671a7fb5029cc3c628d8b05e6
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 01:06:54
    Evidence reason
    redirect
  8. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:06:54.000000
    証拠の SHA-256
    ec71e8bfc1d0d803e8de08ab87c1d3692fd9941671a7fb5029cc3c628d8b05e6
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 01:06:54
    Evidence reason
    redirect
  9. dns_observationunknown
    Observation source
    dns_observation
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 22:56:16.207510
    証拠の SHA-256
    c5f098587335747ecb0284c1aaf394d9a7f57967b624ae64d7c6e3e96d6d5417
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 22:56:16.207510
    Evidence reason
  10. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 13:15:10.000000
    証拠の SHA-256
    9fe0b6ea526ed6b705a3663d9f8187bc7c01ed1568155e7261d9015743d091ed
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 13:15:10
    Evidence reason
    redirect
  11. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 13:15:10.000000
    証拠の SHA-256
    9fe0b6ea526ed6b705a3663d9f8187bc7c01ed1568155e7261d9015743d091ed
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 13:15:10
    Evidence reason
    redirect
  12. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 05:05:27.000000
    証拠の SHA-256
    9f812feb410aaf935d4a8454ee879c399fe72fae27c6461e72fa5715772c9e07
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 05:05:27
    Evidence reason
    redirect
  13. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 05:05:27.000000
    証拠の SHA-256
    9f812feb410aaf935d4a8454ee879c399fe72fae27c6461e72fa5715772c9e07
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 05:05:27
    Evidence reason
    redirect
  14. dns_observationunknown
    Observation source
    dns_observation
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 22:55:15.888363
    証拠の SHA-256
    3b646e5bc1bac379c47f59c89fb9159326ef6c40d3366eb6dfd5fa43e677c4aa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:55:15.888363
    Evidence reason
  15. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 12:57:54.000000
    証拠の SHA-256
    bf314851d6eb1b9d044851377d109bab84e166f4d16290b145e94f52e9065a66
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-22 12:57:54
    Evidence reason
    redirect
  16. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 12:57:54.000000
    証拠の SHA-256
    bf314851d6eb1b9d044851377d109bab84e166f4d16290b145e94f52e9065a66
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-22 12:57:54
    Evidence reason
    redirect
  17. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 04:42:01.000000
    証拠の SHA-256
    5bbb58757d72d7d7c7559e6bdc181f7a4e9f61c0244e8e61b6bad7375af8f646
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-22 04:42:01
    Evidence reason
    redirect
  18. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 04:42:01.000000
    証拠の SHA-256
    5bbb58757d72d7d7c7559e6bdc181f7a4e9f61c0244e8e61b6bad7375af8f646
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-22 04:42:01
    Evidence reason
    redirect
  19. dns_observationunknown
    Observation source
    dns_observation
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 16:53:36.928467
    証拠の SHA-256
    80d44683077929d57cc69d3d485aa4d0ee469673c8067e794714c21730456f32
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 16:53:36.928467
    Evidence reason
  20. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 12:59:37.000000
    証拠の SHA-256
    f8f18a91511721aae9b45b96a86a96acc55ee2d174dffdf9721acfd963550699
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-21 12:59:37
    Evidence reason
    redirect
  21. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 12:59:37.000000
    証拠の SHA-256
    f8f18a91511721aae9b45b96a86a96acc55ee2d174dffdf9721acfd963550699
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-21 12:59:37
    Evidence reason
    redirect
  22. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 04:47:28.000000
    証拠の SHA-256
    05c96674367b2692207a74dd910fac10163d6213a668fa09f7a2334f68b3e4e6
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-21 04:47:28
    Evidence reason
    redirect
  23. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 04:47:28.000000
    証拠の SHA-256
    05c96674367b2692207a74dd910fac10163d6213a668fa09f7a2334f68b3e4e6
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-21 04:47:28
    Evidence reason
    redirect
  24. dns_observationunknown
    Observation source
    dns_observation
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 10:21:37.183325
    証拠の SHA-256
    f6ebc34c637ae5924f85300e39eeddc978e4821086a9222c87005e67a3b0d797
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-20 10:21:37.183325
    Evidence reason
  25. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 04:44:45.000000
    証拠の SHA-256
    071d790ffedc25819611fc96e7a79c097f2be6fbe1f35ede864ce79eb4e28ddd
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-20 04:44:45
    Evidence reason
    redirect
  26. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 04:44:45.000000
    証拠の SHA-256
    071d790ffedc25819611fc96e7a79c097f2be6fbe1f35ede864ce79eb4e28ddd
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-20 04:44:45
    Evidence reason
    redirect
  27. current_http_proberedirected
    Observation source
    current_http_probe
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 13:04:06.000000
    証拠の SHA-256
    717bf9e33d88ef0be3b1759ea528cf9645e873b7372089a94adde3d6918662bf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-19 13:04:06
    Evidence reason
    redirect
  28. http_observationredirected
    Observation source
    http_observation
    原因
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 13:04:06.000000
    証拠の SHA-256
    717bf9e33d88ef0be3b1759ea528cf9645e873b7372089a94adde3d6918662bf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-19 13:04:06
    Evidence reason
    redirect
  29. dns_observationunknown
    Observation source
    dns_observation
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 10:21:20.392196
    証拠の SHA-256
    470b54ea6ccbe7f04a3825ada981b64179b616b50f8ee2944c5c5cf09876edf4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 10:21:20.392196
    Evidence reason
  30. current_state_backfillunknown
    Observation source
    current_state_backfill
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 08:30:46.000000
    証拠の SHA-256
    833730aac3c34d069b9feb367beb33afe96baacbec0016d43acb19c34fc26f49
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 08:30:46
    Evidence reason
  31. http_observationunknown
    Observation source
    http_observation
    原因
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 08:30:46.000000
    証拠の SHA-256
    833730aac3c34d069b9feb367beb33afe96baacbec0016d43acb19c34fc26f49
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 08:30:46
    Evidence reason

記録されたアクティビティ

5 entries
  1. AlienVault OTX

    4 community references

    ソースを表示
  2. VirusTotal

    11/92 engine detections

    ソースを表示
  3. Cloudflare Radar

    Phishing

    ソースを表示
  4. PhishDestroy に登録

    vlodrome.finance

    ソースを表示
  5. URLScan

    Page captured

    ソースを表示

クローキングの確認

ブラウザとクローラーが受け取る内容を比較し、Keitaro によるトラフィック振り分けの有無を確認します。

vlodrome.finance

証拠および外部報告書

詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

4 件の証拠シグナルグループを関連付け済み 最後に確認されたアクティブな状態
認証情報が漏えいした場合は、すぐに報告してください。 被害回復をうたう詐欺業者とは関わらないでください。

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます

自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

共有してしまった情報に応じて、該当する手順を選んでください。このレポートの写しを、ご自身の記録と一緒に保管してください。

今すぐ何をすべきでしょうか?

至急

不審なサイトの利用を中止してください。正規のサービスには、公式アプリか、すでに信頼しているアドレスからアクセスしてください。

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

FBIのガイドライン

元のメール、領収書、メッセージ、スクリーンショットを安全な場所に保管してください。事実に基づく時系列があると、受理する機関が状況を把握しやすくなります。 IC3 evidence guidance ↗

  • 支払い記録 — 支払いをした場合は、領収書、金額、日付、決済サービス、受取人の情報を保存してください。
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) vlodrome.finance)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — 送金した、またはカード情報が漏れた場合は、公式の連絡先から速やかに不正対策窓口に連絡してください。
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

報告したからといって、被害の回復や捜査が保証されるわけではありません。しかし、迅速かつ正確な取引データは、当局やサービス事業者がインシデントを追跡する助けになります。

How do phishing scams typically work?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — 詐欺師が資金回収業者を装い、前払い手数料を要求します。業者を独自に確認するまでは、シードフレーズを教えたり支払ったりしないでください
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

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

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →
このレポートについてソース、観測日、訂正

このレポートは、保存されたページキャプチャ、登録・ネットワーク記録、スキャナーの結果、PhishDestroy の報告履歴をまとめたものです。各ソースにはそれぞれの観測日が保持されています。元の結果を確認するには、各ソースのレポートを開いてください。

AI 支援による分析の作成日時: 。これは作成時点で入手できた証拠に基づくものであり、その後のソース確認によって結果が変わる可能性があります。

キャプチャは、表示されていた内容を記録したものです。スキャナーの結果は、チェック時点におけるその提供元の評価を記録したものです。有効な証明書も、検出ゼロの結果も、安全性を保証するものではありません。

このレポートを埋め込む証拠へのリンク付きのコンパクトなウィジェット
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/embed/domain/vlodrome.finance"
  title="PhishDestroy threat report for vlodrome.finance"
  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>