Hostname
pornzone.com
Last fetched
pornzone.com resolves to 192.150.83.31, announced in 192.150.83.0/24 by TKPSA-AS - P4 Sp. z o.o. in PL. pornzone.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 pornzone.com is recorded in WhisperGraph.
Attribution
p4 sp
MAIL_RECEIVER, ORIGIN_AS
WHOIS identity
- Registrar
- iana:269
- Registrant organisation
- whoisproxy.com
- Contact emails
- info@domain-contact.org, 3234a72d9a493b6f0fb458cf5112f50c23a34c6f33d24568e03d097ff9fb7314@pornzone.com.whoisproxy.org, 8e361632ad4d4973ee7c4015ffaada55b427db877d440be6868f49a513924d19@pornzone.com.whoisproxy.org, cb0443aa09a34bd7db75d023638e9b9f495051400285f7731a9c5ee3aeb61649@pornzone.com.whoisproxy.org, ef163bec06a22dbbd073bd3e827358f71a92c423854504b18248c46138bc00bb@pornzone.com.whoisproxy.org, ff04eefe5a861b0d9e53a669139308396a6b879c499c960e5f8651b0229d9e02@pornzone.com.whoisproxy.org
Subdomains
Showing 5 of 8. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- lex.ns.cloudflare.com
- lily.ns.cloudflare.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
- pornzone.com
SPF policy
- include: _spf.pornzone.com
Threat-feed evidence
History
Related pages
Pivot from pornzone.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: "pornzone.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.