Hostname
cardiology-cloud.com
Last fetched
cardiology-cloud.com resolves to 6 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
cardiology-cloud.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.168.122.108 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.122.12 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.122.51 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.122.7 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 34.199.6.58 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.206.182.248 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
Subdomains
5 observed subdomains of cardiology-cloud.com.
Web-graph footprint
Distinct hostnames that link to or from cardiology-cloud.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
8 SPF mechanisms authorising senders for cardiology-cloud.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 2339900.spf06.hubspotemail.net |
| SPF_INCLUDE | spf.mandrillapp.com |
| SPF_IP | 172.17.1.0/24 |
| SPF_IP | 209.123.145.0/26 |
| SPF_IP | 3.211.246.20/32 |
| SPF_IP | 34.196.39.175/32 |
| SPF_IP | 34.205.109.81/32 |
| SPF_MX | cardiology-cloud.com |
Related pages
Pivot deeper into the graph from cardiology-cloud.com.
- IP · 3.168.122.108
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:146
- Country · US
- Email · lgordon@wrshealth.com
- TLD · .com
- Browse hostnames · ca…
- 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: "cardiology-cloud.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.