Hostname
redi2.com
Last fetched
redi2.com resolves to 44.214.47.175, announced in 44.192.0.0/11 by AMAZON-AES - Amazon.com, Inc. in US. redi2.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
- 44.214.47.175
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.160.62.129
54.160.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for redi2.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:299
- Registrant organisation
- on behalf of redi2.com owner
- Contact emails
- domainmanager@envestnet.com, info@redi2.com, 646210ba-6d76-48ab-8aa9-5d8881bc1998@identity-protect.org, 6645979c-790a-461b-a97e-0183432a950c@identity-protect.org, f8b690cc-82cd-43fc-8661-82e2bdbdeee6@identity-protect.org, owner-12001090@redi2.com.whoisprivacyservice.org, owner-238835@redi2.com.whoisprivacyservice.org, owner-2481048@redi2.com.whoisprivacyservice.org, owner-4915944@redi2.com.whoisprivacyservice.org, owner-5008830@redi2.com.whoisprivacyservice.org, owner@redi2.com.whoisprivacyservice.org
Subdomains
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-11.awsdns-01.com
- ns-994.awsdns-60.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-1244.awsdns-27.org
- ns-1662.awsdns-15.co.uk
MX records
- redi2-com.mail.protection.outlook.com
SPF policy
- include: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email
Threat-feed evidence
History
Related pages
Pivot from redi2.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: "redi2.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.