Hostname
ugghc.com
Last fetched
ugghc.com resolves to 120.76.107.44, announced in 120.76.0.0/17 by ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. in CN. ugghc.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
- 120.76.107.44
120.76.0.0/17 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Shenzhen, CN
- 120.76.107.54
120.76.0.0/17 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Shenzhen, CN
- 139.224.142.114
139.224.128.0/17 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Shanghai, CN
- 139.224.142.124
139.224.128.0/17 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Shanghai, CN
- 39.96.153.44
39.96.0.0/14 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Beijing, CN
- 39.96.153.54
39.96.0.0/14 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Beijing, CN
- 47.118.199.204
47.118.128.0/17 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Hangzhou, CN
- 47.118.199.214
47.118.128.0/17 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Hangzhou, CN
Attribution
hangzhou alibaba advertising
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1599
- Registrant organisation
- domain whois protection service
- Contact emails
- domain@whoisprotectionservice.org
Subdomains
| Subdomain |
|---|
| www.ugghc.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- dns1.hichina.com
- dns2.hichina.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mxbiz1.qq.com
- mxbiz2.qq.com
SPF policy
- include: spf.mail.qq.com
Threat-feed evidence
History
Related pages
Pivot from ugghc.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: "ugghc.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.