Hostname
bkorm.com
Last fetched
bkorm.com resolves to 104.21.65.30, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. bkorm.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.65.30
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.188.187
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for bkorm.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:269
- Registrant organisation
- personal data, can not be publicly disclosed according to applicable laws.
- Contact emails
- 33086b51814b51db467bcb576b6cbcde9187867c64e281fd8fd194203085ad09@bkorm.com.whoisproxy.org, 3ed5fd8f176dcbfe690c9b8b110e3c0a90cc7d82a25fe12b2a4a54294aa89ad5@bkorm.com.whoisproxy.org, 3f67c2ce9f2fe9c1e782b1e7797aedfead9127b1f18d62e17b65d6a81e3ca55e@bkorm.com.whoisproxy.org, 5d3ea5f831ade75e061dbeba2302313d919e20ad620360c04bc57f10cb4acf1d@bkorm.com.whoisproxy.org, 80ed0078cfade44dda1edd5eac116ee9d50f55f5e32aa81f1d482d9ed788c0dd@bkorm.com.whoisproxy.org, a65b71790dd6ab91f0831951f6cffb6c9c6df08f8f88fb4f2806396c12f6e914@bkorm.com.whoisproxy.org, c586f3feaeae64098bf05c066ac2092eef1590b8b83d05eb949468cf319396fd@bkorm.com.whoisproxy.org, e9c564b0b5b545beb27d0cf4cdd3cf764e05366dd59bdecd6398a9b98fb1aff6@bkorm.com.whoisproxy.org, bkorm.com@regprivate.ru
Subdomains
| Subdomain |
|---|
| www.bkorm.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- aarav.ns.cloudflare.com
- eloise.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from bkorm.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bkorm.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.