URLQuery
3 det.
Open reportPhishDestroy first recorded shabi.niniooi.shop on 2026-11-14.
Page title: “秘境视频”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@datacamp.co.uk. The latest stored availability evidence still shows the domain reachable; 8 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Recorded source summary
shabi.niniooi.shop is a subdomain of niniooi.shop. PhishDestroy first observed the hostname on Nov 14, 2026. The captured page title is “秘境视频”. Current evidence score: 90/100 (critical).
Positive findings are stored from 2 sources: Spamhaus DBL and URLQuery. Spamhaus DBL: DBL_SPAM on Nov 14, 2026 at 15:31 UTC. URLQuery recorded 3 detections; no observation timestamp was retained. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Nov 14, 2026 at 15:32 UTC.
An access-restricted HTTP 403 response was recorded on Nov 22, 2026 at 11:10 UTC. Latest classified outcome: protected; cause http access restricted; mechanism access restriction on Nov 22, 2026 at 10:10 UTC. Registration records for the registrable domain niniooi.shop list GNAME.COM PTE. LTD. as the registrar and Aug 8, 2026 as the creation date. At collection time, the hostname resolved to 185.229.190.147 on AS60068 (Datacamp Limited). The recorded endpoint location is Amsterdam, NL. The stored server header is nginx. DOM analysis on Nov 14, 2026 at 15:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 5 visual captures from PhishDestroy, URLScan, Cloudflare Radar, and URLQuery. TLS metadata lists SSL Corporation / SSL.com TLS Issuing RSA CA R1 as the certificate issuer with validity through May 13, 2027; checked Nov 14, 2026 at 17:02 UTC.
The content indicators and 2 positive source findings support the current phishing classification.
3 det.
Open report48/100
spam domain
Scan report
Open reportObserved: · Retrieved:
| UUID | eef59a65-94d2-4aff-b9c7-e0af86907bf7 |
|---|---|
| Final URL | https://shabi.niniooi.shop/ |
| History | URL: https://shabi.niniooi.shop/; Status: 0 |
| Radar rank | Bucket: >200000 |
| DNS records | Name: shabi.niniooi.shop; Type: CNAME; Value: dede0x.b-cdn.net, Name: shabi.niniooi.shop; Type: CNAME; Value: dede0x.b-cdn.net |
| Dnssec valid | ✗ |
Page capture
SHA-256 40a4f3d0…8be3fd5
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
|---|---|
| Crawler rules | Agents: *; Present: ✓ |
| Trackers | Requests: 16 |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 302; Timings: DNS: 0; Wait: 237; Download: 0; Response ms: 282 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443 |
| Carbon | Bytes: 121274; Co2 grams: 0.0044; Cleaner than: 18 |
| DNS server | NS: (IP: 172.64.53.25; Host: a.share-dns.com), (IP: 162.159.27.88; Host: b.share-dns.net); Zone: niniooi.shop |
| Cookies | Cookies: (Name: Load autoe; Session: ✓), (Name: Load img; Session: ✓), (Name: Load url; Session: ✓), (Name: Load time; Session: ✓) |
| Location | IP: 2400:52e0:1e00:2::1329:1; ASN: 60068; Org: Datacamp Limited; City: Eschwege; Country: DE |
| SSL | Issuer: Let's Encrypt / YE1; Subject: shabi.niniooi.shop |
| DNS records | A: 185.111.111.156; Soa: Nsname: ns1.bunnydns.com; Hostmaster: hostmaster.bunnydns.com; Serial: 2022067842; Refresh: 7200; Retry: 900; Expire: 1209600; Minttl: 86400; Aaaa: 2400:52e0:1e00:2::1329:1; Cname: dede0x.b-cdn.net |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Header: max-age=31536000; Message: HSTS header does not include all subdomains. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=31536000; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 2400:52e0:1e00:2::1329:1; Family: 6 |
| Redirects | Chain: https://shabi.niniooi.shop, https://shabi.adinei.shop; Count: 1 |
| Subdomains | Count: 1; Subdomains: shabi.niniooi.shop |
| HTTP headers | Headers: Server: nginx; Content type: text/html; charset=utf-8; Strict transport security: max-age=31536000 |
PhishDestroy rates shabi.niniooi.shop as critical risk (evidence score 90/100) from the recorded evidence; it was first recorded on 2026-11-14. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on shabi.niniooi.shop. A confirmed blockchain transaction cannot be reversed.
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.
3405f6bd2e5ab72771c89499589f0715c55c354770064bcbd34d3fcf0facf106 · 194736 bytes dd2cb10372390719d46f5f77b792899f3bc8afd75502cec63b35821e8fed64a2 · 194899 bytes a5db7ab655d3900bfb2bf44f8483ca7ce06fc6f795376f14b777be50f1f0af62 · 29231 bytes b41f91f3369097d0a1426910bbc11c61a5fc7ca6eab6352550e25d2dd0dc5859 · 440086 bytes Registrable domain behind this subdomain: niniooi.shop. For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
b.share-dns.netnsname: ns1.bunnydns.comhostmaster: hostmaster.bunnydns.comserial: 2022067842refresh: 7200retry: 900expire: 1209600minttl: 86400Location describes the IP network.
633a9458626d8cf2dabcbd5080bf6dd543369941589d8faa5236c01e86752f85*.b-cdn.netb-cdn.netSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was reachable but behind an access challenge at the latest check.
Google PageSpeed Insights — mobile performance audit of shabi.niniooi.shop ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://shabi.niniooi.shop/https://shabi.adinei.shop/Server: nginxContent-Type: text/html; charset=utf-8Content-Encoding: gzipca71912e3cf895eeea14af5f5c20006f6b5414af781ca9f6521483defa6b5e0equic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"keep-alivegziptext/html; charset=utf-8Sat, 14 Nov 2026 15:20:39 GMTnginxmax-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 49 SHA-256 hashes: 49 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-14 15:23 UTC.
Open this scan on URLScan 01a1daa3-a0cb-71da-968b-c8f064d842c6 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
shabi.niniooi.shop Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Behind a check page or access restriction
access restricted · access restriction
Reachable
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 98 d 11 h after registration
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
PD-E4C6B30AAD8169F85EBC Recipient: abuse@datacamp.co.uk 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
shabi.niniooi.shop)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.
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.