Hostname
classyclutter.net
Last fetched
classyclutter.net resolves to 198.99.157.145, announced in 198.99.156.0/22 by TONAQUINT-DC - ValorC3 Data Centers in US. classyclutter.net 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
- 198.99.157.145
198.99.156.0/22 · TONAQUINT-DC - ValorC3 Data Centers · St. George, US
IPv6 resolution
No AAAA record for classyclutter.net is recorded in WhisperGraph.
Attribution
valorc3 centers
ORIGIN_AS
WHOIS identity
- Registrar
- iana:48
- Registrant organisation
- whois agent
- Contact emails
- bwpydgbg@whoisprivacyprotect.com, bynbctqfd@whoisprivacyprotect.com, gddgnxfct@whoisprivacyprotect.com, hxwcddspjb@whoisprivacyprotect.com, kkpgwtwm@whoisprivacyprotect.com, ktgvsrbh@whoisprivacyprotect.com, nxrbdbcc@whoisprivacyprotect.com, pjlwtnhyxy@whoisprivacyprotect.com, tldkrtqm@whoisprivacyprotect.com, vrnwxhfw@whoisprivacyprotect.com, yyhplwhq@whoisprivacyprotect.com
Subdomains
Showing 4 of 4 subdomains (4 per page).
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.orangegeek.com
- ns2.orangegeek.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
- altmx2.orangegeek.net
- altmx3.orangegeek.net
- mx.orangegeek.net
SPF policy
- a: classyclutter.net
- mx: classyclutter.net
- a: mail.orangegeek.net
- mx: mail.orangegeek.net
- ip: 208.67.187.164
Threat-feed evidence
History
Related pages
Pivot from classyclutter.net 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: "classyclutter.net"})-[: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.