Hostname
mellowstate.com
Last fetched
mellowstate.com resolves to 13.227.192.20, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. mellowstate.com 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
- 13.227.192.20
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.33
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.6
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.99
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 18.66.147.105
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.20
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.38
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.59
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.67.13.79
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.67.13.120
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.67.13.40
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.67.13.67
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- dns support
- Contact emails
- mellowstate.com@domainsbyproxy.com, domains@namescompany.com, rwtbllq47ma63g8@proxy.dreamhost.com
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-492.awsdns-61.com
- ns-873.awsdns-45.net
- ns-1190.awsdns-20.org
- ns-2002.awsdns-58.co.uk
MX records
- lgr5ysl32zewod436vbvanlt2kx7kiw2fs23zevywbpi776o6n2q.mx-verification.google.com
- smtp.google.com
SPF policy
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from mellowstate.com 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: "mellowstate.com"})-[: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.