Hostname
roxytheatre.net
Last fetched
roxytheatre.net resolves to 34.213.191.242, announced in 35.1.0.0/16 by AMAZON-02 - Amazon.com, Inc. in US. roxytheatre.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
- 34.213.191.242
35.1.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.216.63.94
35.1.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.161.232.124
35.180.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.228.240.170
45.2.159.0/24 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.253.240.106
45.2.159.0/24 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 50.112.169.128
50.114.5.0/24 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.34.1.94
52.46.5.0/24 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.212.98.216
54.216.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for roxytheatre.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- perfect privacy,
- Contact emails
- wt5bk3na3an@networksolutionsprivateregistration.com, roxy@rangeweb.net
Subdomains
Showing 3 of 3 subdomains (3 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
- ns-107.awsdns-13.com
- ns-835.awsdns-40.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
- ns-1255.awsdns-28.org
- ns-1642.awsdns-13.co.uk
MX records
- mx.roxytheatre.net
SPF policy
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from roxytheatre.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: "roxytheatre.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.