Hostname
transmitsecurity.io
Last fetched
transmitsecurity.io resolves to 15 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
transmitsecurity.io resolves to 15 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.213.92.127 | 18.208.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.218.205.72 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.230.23.215 | 3.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.92.80.235 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.199.5.9 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.199.56.252 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.202.63.39 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.234.134.35 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.235.255.36 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.219.18.233 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.1.77.202 | 52.0.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.203.246.9 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.82.146.29 | 54.80.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.230.116.177 | 3.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | — |
| 13.216.77.29 | 13.216.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | — |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
- —
Subdomains
67 observed subdomains of transmitsecurity.io.
Showing 19 of 67. View all subdomains →
Threat posture
History
Mail and authentication
SPF policy
1 SPF mechanism authorising senders for transmitsecurity.io.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | amazonses.com |
Related pages
Pivot deeper into the graph from transmitsecurity.io.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "transmitsecurity.io"})-[: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.