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

maxisko.bid

In short

PhishDestroy describes maxisko.bid, a page that displays a single message stating the visitor's area was not allowed to access the site.

“maxisko.bid”

Review the evidence
Registrar
United StatesGlobal Domain Group
Resolved IP
South Korea43.164.128.112Shenzhen Tencent Computer Systems Company Limited
Registered
Jul 1, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
92/100
Evidence score
First observed Oct 31, 2026 15:04 UTC · PhishDestroy
Risk signals
VirusTotal detections: 14/92 Spamhaus DBL: spam domain
VirusTotal
14 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 86
Page captures
6
open gallery
Domain age
122 days
registered 2026-07-01 according to WHOIS
OTX: 1 ref Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy describes maxisko.bid, a page that displays a single message stating the visitor's area was not allowed to access the site.

Critical
VirusTotal
14 / 92
Hosting
South Korea43.164.128.112Shenzhen Tencent Computer Systems Company Limited
Registrar
United StatesGlobal Domain Group
Registered
Jul 1, 2026
OTX
1 community ref
Page captures
6
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for maxisko.bid shows a single line of text: "Your area was not allowed to access this site." No form, logo, or other control appears alongside it, so the only interaction available to a visitor is reading this access-denied message. The page gives no indication of which area was blocked or any route to request access, leaving the notice as the entire visible content of the capture.

The stored VirusTotal domain result reports 14 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "phishing".

Source evidenceVirusTotal 14 / 92 · OTX 1 references 8 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
13
Suspicious
1
Undetected
33

Vendor labels

CRDF
malicious
DNS8
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
spam
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.globaldomaingroup.com
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.maxisko.bid
    Value
    ns1.globaldomaingroup.com
  • TTL, seconds
    300
    Type
    A
    Value
    43.164.128.112
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.globaldomaingroup.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d000000d2e61cae37a985f75ecafb81b33ca523

Certificate

Subject alternative names
  • cdn4.viewsite.top
Issuer
Let's Encrypt / YE1
Serial
64a7d3beec67ddd860ee4ae9d8a74bb24cc
SHA-256
89279a8cbd2e25e2ad16e59d7425f17003809414ce0a47fe7d9ffc4a4cab2b84
Subject
cdn4.viewsite.top
Valid until
Valid from

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
Global Domain Group LLC
Registrar IANA ID
3956
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-07-01T09:22:17Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.globaldomaingroup.com"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.maxisko.bid",
        "value": "ns1.globaldomaingroup.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "43.164.128.112"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.globaldomaingroup.com"
    }
]
Dns at
2026-10-08T00:47:08Z
Jarm
27d40d40d00040d00042d43d000000d2e61cae37a985f75ecafb81b33ca523
Certificate
{
    "san": [
        "cdn4.viewsite.top"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "64a7d3beec67ddd860ee4ae9d8a74bb24cc",
    "sha256": "89279a8cbd2e25e2ad16e59d7425f17003809414ce0a47fe7d9ffc4a4cab2b84",
    "subject": "cdn4.viewsite.top",
    "valid_to": "2026-12-06T03:56:22Z",
    "valid_from": "2026-09-07T03:56:23Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-07-01T08:40:18Z",
        "last changed": "2026-07-01T08:40:48Z",
        "registration": "2026-07-01T08:40:18Z",
        "registrar expiration": "2027-07-01T08:40:18Z",
        "last update of RDAP database": "2026-10-07T23:42:10Z"
    },
    "registrar": "Global Domain Group LLC",
    "registrar_iana_id": "3956"
}
Separate source record · 13 malicious + 1 suspicious / 92 · 2026-10-08 00:41:28 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-08T00:41:28Z
fetched_at
2026-10-31T15:06:14Z
stats
{"timeout":0,"harmless":45,"malicious":13,"suspicious":1,"undetected":33}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 86

Open report
URLScanOriginal source recordObserved: 7 fields

Observed: · Retrieved:

Report ID

019f4a3a-e860-7274-919a-16b7f4679ee8

Final URL

https://maxisko.bid/maxis

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

8

Registered domain age, days

8

Page requests

4

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
86
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
019f4a3a-e860-7274-919a-16b7f4679ee8
Final url
https://maxisko.bid/maxis
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
8
Apex age days
8
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 86,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}

OTX

1 community reference

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

748ebfbd-6c3e-450d-b72c-5ae6c3ceea5b

Final URL

https://maxisko.bid/

Navigation history

  • URL
    https://maxisko.bid/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    maxisko.bid
    Type
    A
    Value
    43.164.128.112

DNSSEC valid

No

Registration record

Registrar
Global Domain Group LLC
Registered
Updated
Expires
Nameservers
  • ns2.globaldomaingroup.com
  • ns1.globaldomaingroup.com
Original source fields · JSON
Uuid
748ebfbd-6c3e-450d-b72c-5ae6c3ceea5b
Final url
https://maxisko.bid/
History
[
    {
        "url": "https://maxisko.bid/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "maxisko.bid",
        "type": "A",
        "value": "43.164.128.112"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "Global Domain Group LLC",
    "created": "2026-07-01T08:40:18Z",
    "updated": "2026-08-30T08:40:22Z",
    "expires": "2027-07-01T08:40:18Z",
    "nameservers": [
        "ns2.globaldomaingroup.com",
        "ns1.globaldomaingroup.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

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
maxisko.bid geo-restriction notice shown to visitors
ai_description
PhishDestroy describes maxisko.bid, a page that displays a single message stating the visitor's area was not allowed to access the site.
ai_summary
The captured page for maxisko.bid shows a single line of text: "Your area was not allowed to access this site." No form, logo, or other control appears alongside it, so the only interaction available to a visitor is reading this access-denied message. The page gives no indication of which area was blocked or any route to request access, leaving the notice as the entire visible content of the capture. The stored VirusTotal domain result reports 14 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 16:14:06
revision
ff1f057d23210c2e7aaabf36345662248b384125f18d168bd8396cc0fc51f5d1
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: 14 fields

Mail configuration

SPF lookups
0

CAA records

Domain
maxisko.bid

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
620

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
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    172.64.53.225
    Host
    ns2.globaldomaingroup.com
  • IP address
    172.64.52.97
    Host
    ns1.globaldomaingroup.com
DNS zone
maxisko.bid

Location

IP address
43.164.128.112
ASN
132203
Organization
Shenzhen Tencent Computer Systems Company Limited
City
Seoul
Country
KR

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
cdn4.viewsite.top

DNS records

A
  • 43.164.128.112
NS
  • ns2.globaldomaingroup.com
  • ns1.globaldomaingroup.com
SOA
Primary nameserver
ns1.globaldomaingroup.com
Hostmaster
hostmaster.maxisko.bid
Serial
2026070102
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
43.164.128.112
IP version
4

Registration record

Registrar
Global Domain Group LLC
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns2.globaldomaingroup.com
  • ns1.globaldomaingroup.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "maxisko.bid"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T15:08:11Z",
    "first": "2026-10-31T15:08:11Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 620
}
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": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.53.225",
            "host": "ns2.globaldomaingroup.com"
        },
        {
            "ip": "172.64.52.97",
            "host": "ns1.globaldomaingroup.com"
        }
    ],
    "zone": "maxisko.bid"
}
Location
{
    "ip": "43.164.128.112",
    "asn": "132203",
    "org": "Shenzhen Tencent Computer Systems Company Limited",
    "city": "Seoul",
    "country": "KR"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "cdn4.viewsite.top"
}
DNS records
{
    "A": [
        "43.164.128.112"
    ],
    "NS": [
        "ns2.globaldomaingroup.com",
        "ns1.globaldomaingroup.com"
    ],
    "SOA": "{\"nsname\": \"ns1.globaldomaingroup.com\", \"hostmaster\": \"hostmaster.maxisko.bid\", \"serial\": 2026070102, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "43.164.128.112",
    "family": 4
}
Registration record
{
    "registrar": "Global Domain Group LLC",
    "created": "2026-07-01T08:40:18Z",
    "updated": "2026-08-30T08:40:22Z",
    "expires": "2027-07-01T08:40:18Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns2.globaldomaingroup.com",
        "ns1.globaldomaingroup.com"
    ]
}

Questions about maxisko.bid

Is maxisko.bid legit?

PhishDestroy describes maxisko.bid, a page that displays a single message stating the visitor's area was not allowed to access the site.

Is maxisko.bid safe to connect a wallet?

This report does not record which wallet requests maxisko.bid 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 maxisko.bid?

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 · 6 captures

URLScan · 2026-10-31 1 / 6 Used in the analysis Source file SHA-256: 6d1909d5acf0ed71ed02382b3e72b3f7b81695b548a63742f27ea8cffb9466c0 SHA-256 of the prepared copy given to the model: f1c0977f9c59cc77c7c0650b3f726ea3dba9563e9757eca00db0de908bd268f3
SourceURLScan · 2026-10-31
Recorded
StateStored capture
Final URLhttps://maxisko.bid/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
maxisko.bid
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 35 days

Domain details

Domain
IP Reputation South Korea43.164.128.112 abuse score 0/100 0 reports checked Oct 31, 2026
Registrar Global Domain Group US(US)
Abuse contact["abuse@globaldomaingroup.com", "gdg@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for maxisko.bid →
RegistrationCreated Jul 1, 2026 (122d) — Expires Jul 1, 2027
WHOIS statusclientTransferProhibited
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://maxisko.bid/
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
South Korea43.164.128.112
Network ASN
AS132203
Organization
Shenzhen Tencent Computer Systems Company Limited
Observed location
South KoreaSeoul, KR

Nameservers 2

  • ns2.globaldomaingroup.com
  • ns1.globaldomaingroup.com

SOA

  • nsname: ns1.globaldomaingroup.com
  • hostmaster: hostmaster.maxisko.bid
  • serial: 2026070102
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-07 03:56:23
Valid until
2026-12-06 03:56:22
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint89279a8cbd2e25e2ad16e59d7425f17003809414ce0a47fe7d9ffc4a4cab2b84
Certificate names · 1 SAN
  • cdn4.viewsite.top

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

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

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE

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://maxisko.bid/
forbidden
Response
HTTP 200
HTML body
174 B
Compressed
153 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.22.1
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sat, 31 Oct 2026 15:07:41 GMT
Etag
W/"65a017a3-ae"
Last-Modified
Thu, 11 Jan 2024 16:30:27 GMT
Server
nginx/1.22.1
Transfer-Encoding
chunked

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

Archived

Captured network requests

Network requests: 4 SHA-256 hashes: 3 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-10-31 15:07 UTC.

Open this scan on URLScan 019f4a3a-e860-7274-919a-16b7f4679ee8 ↗

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-10-31 16:07:46.308438
    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 · recorded

Recorded events: 11. 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
    maxisko.bid detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 86
  • 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: 14/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 Recorded: 1 of 1

Recorded activity

5 entries
  1. AlienVault OTX

    1 community references

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    maxisko.bid

    View source
  4. VirusTotal

    14/92 engine detections

    View source
  5. URLScan

    Malicious · engine verdict · score 86

    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.

maxisko.bid

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 14 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 Unverified
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 maxisko.bid)
  • 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/maxisko.bid"
  title="PhishDestroy threat report for maxisko.bid"
  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>