Hostname
classic023.com
Last fetched
classic023.com resolves to 1.56.98.184, announced in 1.56.0.0/13 by CHINA169-Backbone - CHINA UNICOM China169 Backbone in CN. classic023.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
- 1.56.98.184
1.56.0.0/13 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Harbin, CN
- 1.62.64.79
1.56.0.0/13 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Harbin, CN
- 116.131.57.65
116.131.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 116.153.4.244
116.153.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 116.163.31.218
116.163.0.0/18 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Beijing, CN
- 119.167.229.212
119.164.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Jinan, CN
- 157.255.130.195
157.255.130.0/24 · UNICOM-DongGuan-IDC - China Unicom Guangdong IP network · Guangzhou, CN
- 211.93.211.158
211.93.211.0/24 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Beijing, CN
- 211.95.142.138
211.95.142.0/24 · UNICOM-ShenZhen-IDC - China Unicom Guangdong IP network · Shenzhen, CN
- 221.204.15.51
221.204.0.0/15 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Taiyuan, CN
- 221.204.209.225
221.204.0.0/15 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Taiyuan, CN
- 42.56.64.131
42.56.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Shenyang, CN
- 42.56.81.104
42.56.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Shenyang, CN
- 42.56.81.77
42.56.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Shenyang, CN
- 60.13.97.57
60.13.64.0/18 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Haikou, CN
- 175.43.192.174
175.42.0.0/15 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhangzhou, CN
- 123.6.190.169
123.4.0.0/14 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Zhengzhou, CN
- 101.71.88.61
101.71.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Hangzhou, CN
- 116.169.183.111
116.169.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone
- 116.162.168.167
116.162.0.0/16 · CHINA169-Backbone - CHINA UNICOM China169 Backbone · Beijing, CN
IPv6 resolution
No AAAA record for classic023.com is recorded in WhisperGraph.
Attribution
cncgroup ip of shanghai idc
ORIGIN_AS
WHOIS identity
- Registrar
- iana:120
- Registrant organisation
- cheng lianbing
- Contact emails
- domain@whoisprotectionservice.org
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns1.huaweicloud-dns.cn
- ns1.huaweicloud-dns.com
- ns1.huaweicloud-dns.net
- ns1.huaweicloud-dns.org
Threat-feed evidence
History
Related pages
Pivot from classic023.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration and inbound/outbound links.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap)
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.