Hostname
cleancitynetworks.com
Last fetched
cleancitynetworks.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in DE. WHOIS lists iana:1132 as the registrar.
Nutrition Label
Resolution chain
cleancitynetworks.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 |
|---|---|---|---|---|
| 108.138.26.122 | 108.138.24.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 108.138.26.13 | 108.138.24.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 108.138.26.43 | 108.138.24.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 108.138.26.84 | 108.138.24.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.164.240.36 | 3.164.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SE |
| 3.164.240.42 | 3.164.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SE |
| 3.164.240.44 | 3.164.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SE |
| 3.164.240.47 | 3.164.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SE |
WHOIS identity
- Registrar
- iana:1132
- Organization
- dotname domain privacy
- Contact emails
Subdomains
8 observed subdomains of cleancitynetworks.com.
Web-graph footprint
Distinct hostnames that link to or from cleancitynetworks.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for cleancitynetworks.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
Related pages
Pivot deeper into the graph from cleancitynetworks.com.
- IP · 108.138.26.122
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:1132
- Country · DE
- Email · sb.gwon@ecubelabs.com
- TLD · .com
- Browse hostnames · cl…
- 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: "cleancitynetworks.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.