Hostname
renys.com
Last fetched
renys.com resolves to 20.49.104.49, announced in 20.48.0.0/12 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. renys.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 renys.com is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- r.h. reny
- Contact emails
- c235e52a5hr@networksolutionsprivateregistration.com, dx4ja8vq3g3@networksolutionsprivateregistration.com, ek5md8an9ss@networksolutionsprivateregistration.com, hf5jx9nc76x@networksolutionsprivateregistration.com, jx5zt55e26w@networksolutionsprivateregistration.com, m94px44c7dt@networksolutionsprivateregistration.com, qs4qr8dq4b6@networksolutionsprivateregistration.com, rz58s43s4f2@networksolutionsprivateregistration.com, un28k9ff2gz@networksolutionsprivateregistration.com, w57wt3ub5ws@networksolutionsprivateregistration.com, xh3j86yf889@networksolutionsprivateregistration.com
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
- ns39.worldnic.com
- ns40.worldnic.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
- renys-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from renys.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: "renys.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.