Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
nihokei.info favicon

nihokei.info

In short

PhishDestroy describes the connection reset error page captured from nihokei.info, where the browser reported that the site could not be reached.

“nihokei.info”

Review the evidence
Registrar
United StatesSpaceship
Resolved IP
France169.58.38.56Contabo GmbH
Registered
Dec 9, 2025
First observed
Nov 1, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92
VirusTotal
17 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 93
Page captures
8
open gallery
Domain age
327 days
registered 2025-12-09 according to WHOIS · source data differ
OTX: 1 ref Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy describes the connection reset error page captured from nihokei.info, where the browser reported that the site could not be reached.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
France169.58.38.56Contabo GmbH
Registrar
United StatesSpaceship
Registered
Dec 9, 2025
OTX
1 community ref
Page captures
8
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for nihokei.info is a browser error screen rather than a website interface. It displays the heading "This site can't be reached" with the message "The connection was reset" and the error code ERR_CONNECTION_RESET, along with suggestions to check the connection, proxy, or firewall. Two controls are offered: a Details button and a Reload button, which is the main interaction available on this page.

The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 17 / 92 · OTX 1 references 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
14
Suspicious
3
Undetected
32

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    NS
    Value
    launch1.spaceship.net
  • TTL, seconds
    3600
    Type
    A
    Value
    169.58.38.56
  • TTL, seconds
    1800
    Type
    NS
    Value
    launch2.spaceship.net
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    support.spaceship.com
    Value
    launch1.spaceship.net

DNS records observed

JARM fingerprint

15d3fd16d29d29d00042d43d000000f6a76359d2423084924eaeb5187f1701

Certificate

Subject alternative names
  • 02070021.xyz
  • 02070022.xyz
Issuer
Let's Encrypt / YR2
Serial
613ff44812ed08e61e513ff31dc755f7717
SHA-256
899eda6647a7bde1d874f11c7e66e9c87eb285bb71a09e363963178048d2ce72
Subject
02070021.xyz
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
Spaceship, Inc.
Registrar IANA ID
3862
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2025-12-09T00:00:00Z
Updated
2025-12-09T00:00:00Z
First seen
2024-03-05T02:54:54Z
DNS records
[
    {
        "ttl": 1800,
        "type": "NS",
        "value": "launch1.spaceship.net"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "169.58.38.56"
    },
    {
        "ttl": 1800,
        "type": "NS",
        "value": "launch2.spaceship.net"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "support.spaceship.com",
        "value": "launch1.spaceship.net"
    }
]
Dns at
2026-10-29T08:55:41Z
Jarm
15d3fd16d29d29d00042d43d000000f6a76359d2423084924eaeb5187f1701
Certificate
{
    "san": [
        "02070021.xyz",
        "02070022.xyz"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "613ff44812ed08e61e513ff31dc755f7717",
    "sha256": "899eda6647a7bde1d874f11c7e66e9c87eb285bb71a09e363963178048d2ce72",
    "subject": "02070021.xyz",
    "valid_to": "2027-01-14T02:54:19Z",
    "valid_from": "2026-10-16T02:54:20Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-10-19T06:32:25Z",
        "registration": "2025-12-09T07:57:33Z",
        "registrar expiration": "2026-12-09T07:57:33Z",
        "last update of RDAP database": "2026-10-29T08:55:40Z"
    },
    "registrar": "Spaceship, Inc.",
    "registrar_iana_id": "3862"
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-29 08:55:14 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-29T08:55:14Z
fetched_at
2026-11-01T06:33:14Z
stats
{"timeout":0,"harmless":43,"malicious":14,"suspicious":3,"undetected":32}

URLScan

Malicious · engine verdict · score 93

SHA-256 ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

019dd314-bf09-765c-a2a9-fce6c869caa7

Final URL

https://nihokei.info/

HTTP response

404

Redirect type

https-only

Redirects

  • To
    https://nihokei.info/
    From
    http://nihokei.info/
    Status
    307

IP address

188.166.138.69

Contacted IP addresses

  • 188.166.138.69

Autonomous systems (ASN)

  • 14061

Server countries

  • GB

Document hash

ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54

TLS session and certificate

Subject alternative names
  • aliboxinggym.com
Cipher
AES_256_GCM
Issuer
R13
Subject
aliboxinggym.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1168

Differs from the registration date in WHOIS (2025-12-09), which gives 139 days on the scan date 2026-04-28. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1168

Differs from the registration date in WHOIS (2025-12-09), which gives 139 days on the scan date 2026-04-28. The two sources disagree; both values are kept as recorded.

Certificate age, days

7

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
93
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx/1.18.0 (Ubuntu)
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
019dd314-bf09-765c-a2a9-fce6c869caa7
Final url
https://nihokei.info/
Status
404
Redirected
https-only
Redirects
[
    {
        "to": "https://nihokei.info/",
        "from": "http://nihokei.info/",
        "status": 307
    }
]
Ip
188.166.138.69
Contacted IP addresses
[
    "188.166.138.69"
]
Asns
[
    "14061"
]
Countries
[
    "GB"
]
Document hash
ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54
Tls
{
    "san": [
        "aliboxinggym.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "R13",
    "subject": "aliboxinggym.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-07-20T05:10:34Z",
    "valid_from": "2026-04-21T05:10:35Z"
}
Domain age days
1168

Differs from the registration date in WHOIS (2025-12-09), which gives 139 days on the scan date 2026-04-28. The two sources disagree; both values are kept as recorded.

Apex age days
1168

Differs from the registration date in WHOIS (2025-12-09), which gives 139 days on the scan date 2026-04-28. The two sources disagree; both values are kept as recorded.

Tls age days
7
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.18.0 (Ubuntu)",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
019dd314-bf09-765c-a2a9-fce6c869caa7
score
null
malicious
null
result_at
null
enriched_at
2026-11-01T09:12:46Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-01 10:12:46"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

866814a8-d457-44fa-ae81-6dab82ed735c

Final URL

https://nihokei.info/

Navigation history

  • URL
    https://nihokei.info/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    nihokei.info
    Type
    A
    Value
    169.58.38.56

DNSSEC valid

Yes

Registration record

Registrar
Spaceship, Inc.
Registered
Updated
Expires
Nameservers
  • launch1.spaceship.net
  • launch2.spaceship.net
Original source fields · JSON
Uuid
866814a8-d457-44fa-ae81-6dab82ed735c
Final url
https://nihokei.info/
History
[
    {
        "url": "https://nihokei.info/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "nihokei.info",
        "type": "A",
        "value": "169.58.38.56"
    }
]
Dnssec valid
true
Registration record
{
    "registrar": "Spaceship, Inc.",
    "created": "2025-12-09T07:57:33Z",
    "updated": "2026-10-19T06:32:25Z",
    "expires": "2026-12-09T07:57:33Z",
    "nameservers": [
        "launch1.spaceship.net",
        "launch2.spaceship.net"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-11-01T06:50:47Z

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
0
analyzed_at
2026-11-01T06:50:47Z
source_timestamp
2026-11-01 07:50:47
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
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
nihokei.info connection reset error page capture
ai_description
PhishDestroy describes the connection reset error page captured from nihokei.info, where the browser reported that the site could not be reached.
ai_summary
The captured page for nihokei.info is a browser error screen rather than a website interface. It displays the heading "This site can't be reached" with the message "The connection was reset" and the error code ERR_CONNECTION_RESET, along with suggestions to check the connection, proxy, or firewall. Two controls are offered: a Details button and a Reload button, which is the main interaction available on this page. The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 07:36:55
revision
2aa2a65f42a6afda42b76b62cc6e28e7c7442955ea0bc2f04fe695ec31177dec
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 13 fields

Mail configuration

SPF lookups
0

CAA records

Domain
nihokei.info

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
7
Archived days
17
Snapshots per day
0
Average page size, bytes
1881

Trackers

Requests
1

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.159.26.38
    Host
    launch1.spaceship.net
  • IP address
    162.159.27.32
    Host
    launch2.spaceship.net
DNS zone
nihokei.info

Location

IP address
169.58.38.56
ASN
51167
Organization
Contabo GmbH
City
Lauterbourg
Country
FR

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
02070021.xyz

DNS records

A
  • 169.58.38.56
NS
  • launch2.spaceship.net
  • launch1.spaceship.net
SOA
Primary nameserver
launch1.spaceship.net
Hostmaster
support.spaceship.com
Serial
1792395323
Refresh, seconds
43200
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
3600

DNSSEC

DS record
Yes
RRSIG
Yes
DNSKEY
Yes

IP lookup

IP address
169.58.38.56
IP version
4
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "nihokei.info"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-01T06:09:13Z",
    "first": "2008-04-10T15:05:19Z",
    "changes": 7,
    "days_archived": 17,
    "scans_per_day": 0,
    "avg_page_bytes": 1881
}
Trackers
{
    "requests": 1
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.26.38",
            "host": "launch1.spaceship.net"
        },
        {
            "ip": "162.159.27.32",
            "host": "launch2.spaceship.net"
        }
    ],
    "zone": "nihokei.info"
}
Location
{
    "ip": "169.58.38.56",
    "asn": "51167",
    "org": "Contabo GmbH",
    "city": "Lauterbourg",
    "country": "FR"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "02070021.xyz"
}
DNS records
{
    "A": [
        "169.58.38.56"
    ],
    "NS": [
        "launch2.spaceship.net",
        "launch1.spaceship.net"
    ],
    "SOA": "{\"nsname\": \"launch1.spaceship.net\", \"hostmaster\": \"support.spaceship.com\", \"serial\": 1792395323, \"refresh\": 43200, \"retry\": 3600, \"expire\": 604800, \"minttl\": 3600}"
}
Dnssec
{
    "ds": true,
    "rrsig": true,
    "dnskey": true
}
Get ip
{
    "ip": "169.58.38.56",
    "family": 4
}

Questions about nihokei.info

Is nihokei.info legit?

PhishDestroy describes the connection reset error page captured from nihokei.info, where the browser reported that the site could not be reached.

Is nihokei.info safe to connect a wallet?

This report does not record which wallet requests nihokei.info makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used nihokei.info?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 8 captures

Cloudflare Radar 1 / 8 Used in the analysis Source file SHA-256: a5db7ab655d3900bfb2bf44f8483ca7ce06fc6f795376f14b777be50f1f0af62 SHA-256 of the prepared copy given to the model: 9b2bd0fda53e1c8aebf8b218f9819433925b9342fe39730c23b507fc9285f8eb
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://nihokei.info/
Position1 / 8
Open capture Source Report Wayback Download
All capture links and hashes (8)

Domain details

Domain
IP Reputation France169.58.38.56 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar Spaceship US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for nihokei.info →
RegistrationCreated Dec 9, 2025 (327d) — Expires Dec 9, 2026
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://nihokei.info/
Observed page title
404 Not Found
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 73 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
France169.58.38.56
Network ASN
AS51167
Organization
Contabo GmbH
Observed location
FranceLauterbourg, FR
Server header
nginx/1.18.0 (Ubuntu)

Nameservers 2

  • launch1.spaceship.net
  • launch2.spaceship.net

SOA

  • nsname: launch1.spaceship.net
  • hostmaster: support.spaceship.com
  • serial: 1792395323
  • refresh: 43200
  • retry: 3600
  • expire: 604800
  • minttl: 3600

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-16 02:54:20
Valid until
2027-01-14 02:54:19
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint899eda6647a7bde1d874f11c7e66e9c87eb285bb71a09e363963178048d2ce72
Certificate names · 2 SANs
  • 02070021.xyz
  • 02070022.xyz

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

viewdns.info · 169.58.38.56rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://nihokei.info/
nihokei.info
Response
HTTP 200
HTML body
10.6 KB
Compressed
2.1 KB
Links
0 internal · 140 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 14
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 01 Nov 2026 06:10:24 GMT
Etag
W/"6ad5ce76-2a8a"
Last-Modified
Mon, 19 Oct 2026 08:01:58 GMT
Referrer-Policy
same-origin
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-Permitted-Cross-Domain-Policies
master-only
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Archived

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-01 06:35 UTC.

Open this scan on URLScan 019dd314-bf09-765c-a2a9-fce6c869caa7 ↗

All retained availability observations1

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_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 08:01:04.835385
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    nihokei.info detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 93
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. AlienVault OTX

    1 community references

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    nihokei.info

    View source
  4. VirusTotal

    17/92 engine detections

    View source
  5. URLScan

    Malicious · engine verdict · score 93

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

nihokei.info

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including nihokei.info)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
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

Embed This Report

Share this threat intelligence on your website or blog

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