Hostname
tightasspics.com
Last fetched
tightasspics.com resolves to 204.155.154.47, announced in 204.155.154.0/24 by WZ-US-40824 - Webzilla Inc. in US. tightasspics.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
IPv6 resolution
No AAAA record for tightasspics.com is recorded in WhisperGraph.
Attribution
webzilla
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1418
- Registrant organisation
- moniker privacy services
- Contact emails
- tightasspics.com@whoisprotectservice.net, 07836b2d3cc79bf35f06c49e842e7772697552a095cdcd2bf4c6e4bec577080b@tightasspics.com.whoisproxy.org, 2337a174ef0bb8b02ee78fe170452935a5a25ac39dab8aa1c74a548fd416d418@tightasspics.com.whoisproxy.org, 4652d8e386c75288c6f3e6355bb63b4c876075eb4ba64191f72f86b52059780a@tightasspics.com.whoisproxy.org, 78a7b8a9feb6a6bedf7b7337b8452713d1b5f9621c9700271c76155cd0e357e4@tightasspics.com.whoisproxy.org, 7dffc948c7017126e46c4f8fdc0639a0e057fb10fed1b396125848b2fca4cf50@tightasspics.com.whoisproxy.org, 9f82bd7bfa011ed2d1daa5b8ba4370dba579047b27a777c7a12af73506cff8f1@tightasspics.com.whoisproxy.org, d05edc7657d50c09cc15d6454ea833d13b55fe2d31f0e042fb72e8e2de9f24bf@tightasspics.com.whoisproxy.org
Subdomains
Mail and authentication
Nameservers
- ns1.tightasspics.com
- ns2.tightasspics.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
Threat-feed evidence
History
Related pages
Pivot from tightasspics.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: "tightasspics.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.