Hostname
tweepi.com
Last fetched
tweepi.com resolves to 100.31.228.125, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. tweepi.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
- 100.31.228.125
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.211.253.21
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.227.252.185
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.4.222.201
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.161.212.173
54.160.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.195.5.227
32.192.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for tweepi.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- ******** ******** (see notes section below on how to view unmasked data)
- Contact emails
- ********@*****.***, amer@thoughtpick.com, contact+gd@tweepi.com, contact@tweepi.com
Subdomains
Showing 4 of 5. 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
- ns-344.awsdns-43.com
- ns-930.awsdns-52.net
- ns-1304.awsdns-35.org
- ns-2025.awsdns-61.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: _spf.google.com
- a: tweepi.com
- mx: tweepi.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from tweepi.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: "tweepi.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.