Hostname
transitdatascience.com
Last fetched
transitdatascience.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in CO. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
transitdatascience.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.163.58.132 | 3.163.56.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.163.58.179 | 3.163.56.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.163.58.194 | 3.163.56.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.163.58.196 | 3.163.56.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 99.84.231.149 | 99.84.230.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.231.167 | 99.84.230.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.231.45 | 99.84.230.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.231.88 | 99.84.230.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of transitdatascience.com owner
- Contact emails
- 67ea8b51-e0cd-4989-9b0f-feeb061ee8b5@identity-protect.org
- 86f0cde8-563e-4803-a3ab-88e3073c6286@identity-protect.org
- 8ce6517f-2b13-4359-baa9-03a710ff55e8@identity-protect.org
- eb62c2eb-3a28-424b-bd42-7825b83ea265@identity-protect.org
- f1641637-cf53-470d-9053-bb0df99af7ed@identity-protect.org
- fcad29c9-0a6c-41e6-8c10-33c873dc9da4@identity-protect.org
Threat posture
History
Mail and authentication
MX records
Related pages
Pivot deeper into the graph from transitdatascience.com.
- IP · 3.163.58.132
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · CO
- Email · 67ea8b51-e0cd-4989-9b0f-feeb061ee8b5@identity-protect.org
- TLD · .com
- Browse hostnames · tr…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "transitdatascience.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.