Hostname
clean.cloud
Last fetched
clean.cloud resolves to 18.118.54.62, announced in 18.116.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. clean.cloud is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 18.118.54.62
18.116.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.119.204.221
18.116.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.188.57.16
18.188.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.225.73.110
18.224.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.227.199.194
18.224.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.13.133.236
3.13.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.132.91.42
3.132.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.138.48.147
3.136.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.147.198.19
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.149.168.6
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.19.186.76
3.16.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.21.119.52
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 16.58.144.101
IPv6 resolution
No AAAA record for clean.cloud is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- blue safety
- Contact emails
- clean.cloud@domainsbyproxy.com, moenninghoff@bluesafety.com
Mail and authentication
Nameservers
- ns-124.awsdns-15.com
- ns-814.awsdns-37.net
- ns-1487.awsdns-57.org
- ns-1872.awsdns-42.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- mx: clean.cloud
- include: spf.autopilothq.com
- include: _spf.google.com
- include: mail.zendesk.com
- include: servers.mcsv.net
- include: sendgrid.net
- include: eu.zcsend.net
Threat-feed evidence
History
Related pages
Pivot from clean.cloud into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "clean.cloud"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.