technology software

documentation technical

cryptocurrency blockchain

government public service

English

You're looking at domain '124.221.210.109:8080' on an unknown top-level domain with no subdomain. The registrable portion '124.221.210.109' spans 15 characters containing 0 vowels alongside 0 consonants, notching twelve digits. Word splitting yields 4 words: 124, 221, 210, 109. Average segment length settles at three characters. No strong language cues emerged from the frequency lists.

f33a2d78362bde001670e3a29b01fd0dc16a7f9194d042a775af89270ab38b74

1499a72ba22ab7037f8f23dc9f0a84d8c2c0f8e83b641bef56d90d4831a9a696

0819bcc6e721827a284f1d3b19335fcf0c123121e60e87c9302f4ccf639dba05

11e82953f9a1018a12e8843795c7e69112ec18628a15357de12aac7342230a5b

9c17cab6ab49fda358227f1e1015fa8f2417614e37ce3d4756edf8269ad3c97c

0adb816ede01a8d73722a30487533bbbb0106a83bccfdf04b13d10a422a75870

7d876707e753974b80e455561e82dff0e7f7a0fa408c584003ead9ea337f75bf

e9f2925331e26ca5b93a2289d00640113768fe8d394ae8e315f7b2ce5c288815

e9bdb89b169c20f98f21599c8bfe757bf7da088c82d855c22f5ce310b693828a

15674a3df509754c0236a55dc8a8eb325bd0de65c28863ca9f2c862fcb81ff0e

807da6f7d8a9efd4b81a57f7a4c0a9fa80abe61cd916605f26c713004acaf95d

df66b929dbb1bef6f8ab9303a388a9818aa1e521e5963486b0e8988cbcd99b63

3a98d852b6bee7154f063223d0ee6f578472dad5a58f5dbd03dcf31d8d0800b8

9171e077e93a2f5b95e0a7621996661b19d995018594865b565a716c6a2ffe60

dafc2088fb1e331cba988f488815373e0c29ebf2b202b11cda5527daf66debf1

3b5487325a3d39721adf0b06085df3aa30becc032b423b19c303183aa62dce88

2edba5f95d5416fe670fabca0600263920d52d70f2203353d75ed189139f05ec

d09f797b58e932cfb635090b38b0e858102a6278a850835aa3b0ef435b332278

f4307c4dc8127a6d3c19096af6154b3517af510e3442e35a0f914e3c03d4963f

ea0eab54c3e66a722490ac2143a7569e01e8f5816ba0a7495240535c2c9e8388

2c99f7ba681a034774eed4b8482190e755252193de24d3531308159275b35a53

4265f0268480ac9444c24a28837751ed926640ac0440c0300edbda91d2b9f18d

0ec98caf6fcd35c25aeff12293e8aaa73efd1dfe3dfc1b19c6a428d6c80529fa

a79120166b9968eb700c60162c326a55962252a70d865bdfcca0abbaa4a97764

81b7ad513e3ebcf0b8c6bb88e9a6d0ea04e26f42f4e46a8c97a6735ecdbabbf3

49b36e8c9bb53d44f618d62eb8d5bf89a480e4817ad4b0280990f9197d378875

f892f91e895ccfdb599baadb94e4d0f84f3d42db861050999609416313c07448

f120d81c79b8069bbc362f9bf186f8724980a1c21afb3460f781e94e6db06bd1

c9506197caf809a075b6dee1da0d36fb19da7158ffe8a88e7b0c96c5d8623c99

192a46c98c2b16b82a1332d347ad87233f78246223ff1f98dc94747ce331a21e

630877bb6e77257d6c06e156c3f402a1c4f2eb53ea96e6e3169787fdd7e9b0b8

8eb1ecf1bbb816baaa0c738501d2996c7a695da29564466062417f70f4f17a39

ee9e17df39407bc9aac960e1eaa0a9cb1f530e596943026de95bdaf7a8c4eefe

323bac53f364f9248f08c10c8daaeac91e848b5d413135b5b6c78d8dd255ef4c

bf90cd21c3a6232ffd6688d08290a42829535a718d35a8a1cc46fd01adb8230b

23c8b3c2edea285a74ad81b26da4cdf35bb5a5269b2941969cfba33840fdb153

0c1201ffc90c4ea6046754efe27c6d3d17ab74df6680d7395dfa4e5eb3c661dc

d6e505b2efe95e9884d64ca103cabcd7c8c1cd48976f7dd202af4c4c90e9aba9

73d780a1d6ec10788c6ae7da42af7150e0fe657879751832882b7dbc1c7c2073

9a3c6083d018e4067453f20f3e7318eacf0916471e37fb1ba4327231d87b296c

f8a966da313418fd70fbab47ae2c4fb0fc91ca017cf576c65dfe3ac2c2cf172d

069b58bb65d96b5a652ce834cccd1d5839c9cc564768bf16c2ab6f9736481480

aa4134d8bd249b1a865a0e5a1b83c6258813d79a65789da894102772f39f4c36

f6837d1404ce1f989fd02ec9041454077d3eaa22f943437ad7c174dcccca50ba

a15e177cbc955a3bf4f4fc9dd551499e720afee7c8a4d5a609154e04c524c4ca

fb2e4da2609e71417ed6f82045ea2d45a4de28a221234e3a04eed13afce1b484

d0327b8f3c11fb3f1c4f11a7fdb557657f136600ace1b038473f0be85283d1cf

2b320df5198c556a6017bd273a8b4fe8567f18d287bcdc120c4870b62bf49751

DOMPurify allows tampering by prototype pollution

DOMPurify allows Cross-site Scripting (XSS)

When USE_PROFILES is enabled, DOMPurify rebuilds ALLOWED_ATTR as a plain array whose properties are looked up by name, making it susceptible to prototype pollution. If Array.prototype has been polluted with an event handler attribute name (e.g. onclick), DOMPurify will allow that event handler to survive sanitization, resulting in DOM-based XSS.

DOMPurify's ADD_ATTR predicate function mechanism (via EXTRA_ELEMENT_HANDLING.attributeCheck) short-circuits URI validation when the predicate returns true. This allows unsafe protocols such as javascript: to survive sanitization in href and similar attributes, enabling DOM-based XSS when such links are activated.

DOMPurify is vulnerable to mutation-XSS (mXSS) when sanitized HTML is embedded into special raw-text wrapper elements such as xmp, script, iframe, noembed, noframes, or noscript before being assigned via innerHTML. Attacker-controlled sequences like </xmp> inside attribute values close the raw-text context during the second parse, causing the sanitized output to mutate into executable markup.

DOMPurify has a logic inconsistency where FORBID_TAGS is not checked when a function-based ADD_TAGS (tagCheck) returns true. Due to short-circuit evaluation, the FORBID_TAGS check is never evaluated, allowing explicitly forbidden elements to pass through sanitization when EXTRA_ELEMENT_HANDLING.tagCheck is configured.

DOMPurify has an asymmetric security inconsistency where FORBID_TAGS does not win over a function-based ADD_TAGS predicate, while FORBID_ATTR correctly wins over ADD_ATTR. When ADD_TAGS is provided as a function that returns true, explicitly forbidden tags such as iframe and form pass through sanitization with their attributes intact.

DOMPurify's SAFE_FOR_TEMPLATES feature fails to strip Mustache/template expressions when RETURN_DOM or RETURN_DOM_FRAGMENT is used. The final string-scrubbing pass that removes expressions like {{...}} is skipped in DOM-return mode, and split text nodes (e.g. from removed intermediate tags) can rejoin to form a complete expression that template-evaluating frameworks like Vue 2 will execute.

DOMPurify versions 3.0.1 through 3.3.3 are vulnerable to an XSS bypass via prototype pollution. When no CUSTOM_ELEMENT_HANDLING is specified, the fallback plain object inherits from Object.prototype; if an attacker has polluted Object.prototype.tagNameCheck and Object.prototype.attributeNameCheck with permissive regexes, DOMPurify allows arbitrary custom elements with event handler attributes through sanitization.

DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks

DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM

DOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`

DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.content

DOMPurify: `IN_PLACE` mode trusts attacker-controlled `nodeName` on live non-form nodes, allowing script retention and XSS via attacker-supplied DOM objects

DOMPurify: SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside <template> content when using DOM output modes

DOMPurify: Trusted Types policy survives `clearConfig()` and can poison later `RETURN_TRUSTED_TYPE` output

DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)

DOMPurify: `CUSTOM_ELEMENT_HANDLING` bypasses `afterSanitizeElements` for allowed custom elements.

DOMPurify: IN_PLACE hook removal leaves a detached subtree executable, causing XSS

DOMPurify: IN_PLACE returns a force-removed rawtext root whose text carries attacker markup — pure HTML reparse executes

DOMPurify: SMIL attributeName=href guard is skipped when PARSER_MEDIA_TYPE is application/xhtml+xml

DOMPurify IN_PLACE: hook that removes a parent or sibling leaves the detached subtree's event handlers armed (incomplete fix for GHSA-p98j-92pf-mc4p)

4ed913f5ffd0817b8c0df7e6e4c535efb1e6c1eb7b8069f53af12b9e90109eef

33fcafc31a013417c087daa44b6a56303b7c62ef9b420f609845e3a323d67521

42cccc555b63847fca74c26f66a2754cd463ba24015a028b3d792c3851e40b1d

d5773718215a5102823dcf0be71426eea2c95d96ed323f6c8de9f015e95c3bdc

width=device-width, initial-scale=1.0, viewport-fit=cover, interactive-widget=resizes-content

viewport

theme-color

format-detection

mobile-web-app-capable

apple-mobile-web-app-capable

apple-mobile-web-app-status-bar-style

apple-mobile-web-app-title

HSTS header missing - vulnerable to protocol downgrade attacks

CSP header missing - vulnerable to XSS attacks

James Tian

Jimmy Xiao

TencentCloud


        (function () {
            var initialPage = String(window.location.hash || '').replace(/^#/, '').split('?')[0];
            if (initialPage && initialPage !== 'dashboard') {
                document.documentElement.classList.add('initial-route-pending');
            }
        })();
    


        
        if (typeof ELK === 'undefined' && typeof elk !== 'undefined') {
            window.ELK = elk;
        }
    

Marked

CyberStrikeAI

regular

⚠️ High Risk - http://124.221.210.109:8080/

Requests	IP Address	Location	AS Autonomous System
60	124.221.210.109	Shanghai, Shanghai, China	AS45090Shenzhen Tencent Computer Systems Company Limited
60	1	-	-

Security Scan Report: 124.221.210.109

Summary

AI Security Verdict

High Risk

Details

Screenshot

Page Load Overview

Language Analysis

Primary Language

Detection Details

Website Classification

Primary Category

All Detected Categories

Detected Features

Domain & IP Information

Detected Technologies1

Content Similarity HashesFor malware variant detection

TLSH (Trend Micro Locality Sensitive Hash)

ssdeep (Context Triggered Piecewise Hashing)

sdhash (Similarity Digest Hashing)

Image Hashes

Perceptual Hashes

Other Hashes

Scan History