Hostname
622966.com
Last fetched
622966.com resolves to 208.98.40.201, announced in 208.98.40.0/24 by SHARKTECH - Sharktech in US. 622966.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
- 208.98.40.201
208.98.40.0/24 · SHARKTECH - Sharktech · Chicago, US
- 208.98.40.207
208.98.40.0/24 · SHARKTECH - Sharktech · Chicago, US
- 208.98.40.215
208.98.40.0/24 · SHARKTECH - Sharktech · Chicago, US
- 47.76.127.217
47.76.0.0/17 · ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. · Hong Kong, HK
- 47.91.170.222
47.91.128.0/18 · ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. · Hong Kong, HK
- 8.218.208.240
8.218.128.0/17 · ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. · Hong Kong, HK
- 208.98.43.75
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.43.77
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.43.13
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.43.19
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.43.11
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.43.74
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.40.74
208.98.40.0/24 · SHARKTECH - Sharktech · Los Angeles, US
- 208.98.43.79
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
- 208.98.40.229
208.98.40.0/24 · SHARKTECH - Sharktech · Los Angeles, US
- 208.98.43.91
208.98.43.0/24 · SHARKTECH - Sharktech · Acton, US
IPv6 resolution
No AAAA record for 622966.com is recorded in WhisperGraph.
Attribution
sharktech
ORIGIN_AS
WHOIS identity
Subdomains
| Subdomain |
|---|
| www.622966.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns1.4.cn
- ns2.4.cn
- www.622966.com
- ns1.alidns.com
- ns2.alidns.com
- ns3.goldenname.com
- ns4.goldenname.com
- dns31.hichina.com
- dns32.hichina.com
Threat-feed evidence
History
Related pages
Pivot from 622966.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: "622966.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.