Hostname
iotemerge.com
Last fetched
iotemerge.com resolves to 6 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:447 as the registrar.
Nutrition Label
Resolution chain
iotemerge.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 |
|---|---|---|---|---|
| 100.27.154.59 | 100.24.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 13.222.70.163 | 13.216.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.226.2.153 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.230.170.180 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 35.171.138.184 | 35.168.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.82.254.78 | 54.80.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:447
- Organization
- domain admin
- Contact emails
Subdomains
2 observed subdomains of iotemerge.com.
| Subdomain |
|---|
| m.iotemerge.com |
| www.iotemerge.com |
Web-graph footprint
Distinct hostnames that link to or from iotemerge.com in the public web crawl.
13 sites link to this hostname.
1 site linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
7 SPF mechanisms authorising senders for iotemerge.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _netblocks.mimecast.com |
| SPF_INCLUDE | penton.com |
| SPF_IP | 4.53.192.107 |
| SPF_IP | 67.208.32.112 |
| SPF_IP | 8.33.3.81 |
| SPF_IP | 8.33.3.82 |
| SPF_MX | iotemerge.com |
Related pages
Pivot deeper into the graph from iotemerge.com.
- IP · 100.27.154.59
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:447
- Country · US
- Email · domain_admin@penton.com
- TLD · .com
- Browse hostnames · io…
- 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: "iotemerge.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.