VirusTotal
16 / 91 engine detections
Open reporttokyosanno.com is a Wordpress impersonation page detected by PhishDestroy on 2026-09-18. Risk: critical (100/100). Registrar: Japan Registry Services. Status: Last known active. Hosting: NTT DOCOMO BUSINESS,Inc. VirusTotal: 16/91 engines flag it. Do not enter credentials or connect a wallet.
16 / 91 engine detections
Open report30 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
tokyosanno.com is classified by PhishDestroy as an impersonation phishing page: a site that presents itself as someone it is not in order to win visitors' trust. Its targets are people who believe they are dealing with a legitimate organisation and act on that belief. PhishDestroy first flagged it on 2026-09-18. On 2026-10-19 the site was still online and serving live content.
Impersonation pages copy the look, wording and branding of an organisation the victim already trusts. Visitors are then steered toward an action that benefits the operator, such as signing in, filling in a form with personal or payment details, or sending money. Because the page feels familiar, victims rarely question it. What they lose depends on what they type in. Account passwords can be used to take over the real account, while card or banking details can lead to direct financial loss.
On 2026-09-29, 16 of 91 VirusTotal engines flagged the domain. They include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, ADMINUSLabs and CyRadar. That is a minority of engines, but the flagging group mixes major antivirus vendors with specialist URL classifiers, so the verdict does not rest on a single source. The domain also appears in 30 AlienVault OTX threat pulses, which shows other researchers have been tracking it. Among public blocklists, it is currently listed by PhishDestroy.
The domain was registered on 2011-11-28, nearly fifteen years before PhishDestroy detected it. That is an unusually long history compared with the throwaway domains common in phishing. Its registrar is Japan Registry Services Co., Ltd., and the site is hosted in Japan on the NTT DOCOMO BUSINESS, Inc. network. It also holds an organisation-validated TLS certificate from JPRS. Visitors should not read the padlock or the certificate type as proof that the page is safe to use.
If you entered a password on this site, change it right away on the real service and on any other account that shares it. Turn on two-factor authentication and review recent sign-ins. If you submitted card or bank details, contact your bank to block the card and dispute unfamiliar charges. If you shared personal information, watch for follow-up phishing messages that use it. Security teams should block tokyosanno.com at the DNS and proxy layer, search mail and web logs for users who visited it, and reset credentials for anyone who interacted with it.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019fca52-f7e3-7629-80f7-40c0fb8140f9 |
|---|---|
| Final url | https://tokyosanno.com/www.paypal-resolution.center.co.uk/encripted/ssl218.site/identification.html |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://tokyosanno.com/www.paypal-resolution.center.co.uk/encripted/ssl218.site/identification.html",
"from": "http://tokyosanno.com/www.paypal-resolution.center.co.uk/encripted/ssl218.site/identification.html",
"status": 307
}
] |
| Ip | 60.43.158.50 |
| Ptr | tokyosanno.com |
| Contacted IP addresses | [
"60.43.158.50"
] |
| Asns | [
"4713"
] |
| Countries | [
"JP"
] |
| Document hash | d844cdc5c949c88c9acc74d7fc1bce9614484631fb86ba5501912d15046a4dbc |
| Tls | {
"san": [
"*.bizmw.com",
"bizmw.com"
],
"cipher": "AES_128_GCM",
"issuer": "JPRS Organization Validation Authority - G4",
"subject": "*.bizmw.com",
"protocol": "TLS 1.2",
"valid_to": "2026-10-31T14:59:59Z",
"valid_from": "2025-10-01T00:06:06Z"
} |
| Domain age days | 1265 |
| Apex age days | 1265 |
| Tls age days | 307 |
| Tls valid days | 395 |
| Requests | 2 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": -47,
"malicious": false
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Apache",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "PHP/7.4.33"
} |
Observed: · Retrieved:
| Uuid | 71af4d71-2a81-43b3-a41e-d8b81a371105 |
|---|---|
| Final url | https://tokyosanno.com/ |
| History | [
{
"url": "https://tokyosanno.com/",
"status": 0
}
] |
| DOM structure hash | f7a48cc844a2898cdb50aa55394e2633ea45e5ef13dc1aed1292ed349b65d815 |
| Domain risks | [
"Government/Legal",
"Government & Politics"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "tokyosanno.com",
"type": "A",
"value": "60.43.158.50"
}
] |
| Dnssec valid | false |
| Registration record | {
"registrar": "Japan Registry Services Co., Ltd.",
"created": "2011-11-28T02:25:28Z",
"updated": "2025-11-23T15:19:04Z",
"expires": "2026-11-28T02:25:28Z",
"nameservers": [
"mwns1.customer.ne.jp",
"mwns2.customer.ne.jp"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 17,
"suspicious": 0,
"undetected": 31
} |
|---|---|
| Vendor labels | {
"ESET": "phishing",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"URLQuery": "malicious",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "phishing",
"ADMINUSLabs": "malicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"Sophos": "phishing and fraud",
"Webroot": "Phishing and Other Frauds",
"alphaMountain.ai": "Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds. political organizations"
} |
| Registrar | Japan Registry Services Co., Ltd. |
| Created | 2011-11-28T02:25:28Z |
| Expires | 2026-11-28T02:25:28Z |
| Updated | 2025-11-23T15:19:04Z |
| First seen | 2023-10-02T00:28:29Z |
| DNS records | [
{
"ttl": 3600,
"type": "NS",
"value": "mwns2.customer.ne.jp"
},
{
"ttl": 3600,
"type": "SOA",
"rname": "host-plan-ac.ntt.com",
"value": "mwns1.customer.ne.jp"
},
{
"ttl": 3600,
"type": "MX",
"value": "mwbgw2.ocn.ad.jp",
"priority": 10
},
{
"ttl": 3600,
"type": "TXT",
"value": "v=spf1 a include:_spf.bizmw.com ~all"
},
{
"ttl": 3600,
"type": "NS",
"value": "mwns1.customer.ne.jp"
},
{
"ttl": 3600,
"type": "MX",
"value": "mwbgw1.ocn.ad.jp",
"priority": 10
},
{
"ttl": 3600,
"type": "A",
"value": "60.43.158.50"
}
] |
| Dns at | 2026-10-13T12:07:18Z |
| Jarm | 07d2ad16d21d21d00007d2ad07d21dd7d473c13818c4075312b20b785cad90 |
| Certificate | {
"san": [
"*.bizmw.com",
"bizmw.com"
],
"issuer": "Japan Registry Services Co., Ltd. / JPRS Organization Validation Authority - G4",
"serial": "7cd4391fd1d8e685bca660716f757efc",
"sha256": "7f416447b0b15808aa15335abec08c56abb826534528c304c943d9e036f0a7dd",
"subject": "*.bizmw.com",
"valid_to": "2026-10-31T14:59:59Z",
"valid_from": "2025-10-01T00:06:06Z"
} |
| Registration record | {
"registrar": "Japan Registry Services Co., Ltd.",
"registrar_iana_id": "1485",
"registrar_url": "http://jprs.jp/registrar/",
"created": "2011-11-28T02:25:28Z",
"updated": "2025-11-23T15:19:04Z",
"expires": "2026-11-28T02:25:28Z",
"status": [
"ok"
],
"nameservers": [
"mwns1.customer.ne.jp",
"mwns2.customer.ne.jp"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"last changed": "2025-11-23T15:19:04Z",
"registration": "2011-11-28T02:25:28Z",
"registrar expiration": "2026-11-28T02:25:28Z",
"last update of RDAP database": "2026-10-10T23:23:23Z"
}
} |
No. PhishDestroy classifies tokyosanno.com as a Wordpress impersonation page (risk: critical, 100/100); it was first detected on 2026-09-18. VirusTotal: 16/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on tokyosanno.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
mwns2.customer.ne.jpmwbgw2.ocn.ad.jppriority 10mwbgw1.ocn.ad.jppriority 10Location describes the IP network.
7f416447b0b15808aa15335abec08c56abb826534528c304c943d9e036f0a7ddbizmw.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
tokyosanno.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
14→15
30 community references
View sourceNo threat flag
View source16/91 engine detections
View sourcetokyosanno.com
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
tokyosanno.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.