Hostname
grenserv.com
Last fetched
grenserv.com resolves to 104.21.35.108, announced in 104.22.2.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. grenserv.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
- 104.21.35.108
104.22.2.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.218.32
172.68.19.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.116.121.209
18.126.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.116.75.179
18.126.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.116.95.186
18.126.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.226.234.48
18.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.135.117.181
3.132.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.146.80.235
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.147.138.122
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.151.155.142
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.151.56.152
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.18.196.148
3.16.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.20.37.96
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 16.58.99.15
16.59.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of grenserv.com owner
- Contact emails
- be350f2c-b1b4-4f3b-9eb9-8b1e0abc2eb0@identity-protect.org, d8f3bfb1-80fd-4c5d-8cf6-7ee6dbfea1b3@identity-protect.org
Mail and authentication
Nameservers
- ns-433.awsdns-54.com
- elliot.ns.cloudflare.com
- surina.ns.cloudflare.com
- ns-710.awsdns-24.net
- ns-1125.awsdns-12.org
- ns-1713.awsdns-22.co.uk
Threat-feed evidence
History
Related pages
Pivot from grenserv.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: "grenserv.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.