Hostname
prince.com
Last fetched
prince.com resolves to 104.248.109.253, announced in 104.248.108.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. prince.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.248.109.253
104.248.108.0/22 · DIGITALOCEAN-ASN - DigitalOcean, LLC · North Bergen, US
IPv6 resolution
No AAAA record for prince.com is recorded in WhisperGraph.
Attribution
digitalocean
ORIGIN_AS
WHOIS identity
- Registrar
- iana:470
- Registrant organisation
- domain manager
- Contact emails
- 2751461@privacy-link.com, admin@comlaude.com, prince.com-registrant@anonymised.email, 04541b70874abd3082042414b868477eabedeb2dcc4d3908732476e11ae385f4@prince.com.whoisproxy.org, 129341e8473051f667cc7b10bb399058663db7b12b026e3d97b3c40b1b93a3b5@prince.com.whoisproxy.org, 4d661df035975593c6c887913cf08d154328df018e76f6ee5a3d1f4893404a49@prince.com.whoisproxy.org, 6f99b20666a8a9cc50760e4d677f0e0bbb1bb437dc0f9fcdea5e15c5b9f52639@prince.com.whoisproxy.org, cee215df2e9e95a6207d51f7ce1b2c3e56ceb9d475477230b0f78d9d48e060a2@prince.com.whoisproxy.org, de639397d6cd0d6aa4917f0f997c20a7cb63baffe119e8cd20b8219072e315af@prince.com.whoisproxy.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.
Mail and authentication
Nameservers
- ns1.mediatemple.net
- ns2.mediatemple.net
- 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
Threat-feed evidence
History
Related pages
Pivot from prince.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: "prince.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.