Hostname

greenguarddc.org

Last fetched Sun, 13 Sep 2026 18:19:01 GMT

greenguarddc.org resolves to 34.120.137.41, announced in 34.120.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. greenguarddc.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

34.120.137.41
34.120.0.0/14 · GOOGLE-CLOUD-PLATFORM - Google LLC · Kansas City, US
84.32.84.224
84.32.84.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
92.113.16.185
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
92.113.16.246
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
92.113.16.75
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
92.113.23.15
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
92.113.23.233
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
92.113.23.52
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
2.57.91.178
2.57.91.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT

IPv6 resolution

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar: iana:1636
Registrant organisation: privacy protect, llc (privacyprotect.org)

Subdomains

Subdomain
www.greenguarddc.org

Showing 1 of 1 subdomain (1 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

ns1.dns-parking.com
ns2.dns-parking.com

MX records

mx1.hostinger.com
mx2.hostinger.com

SPF policy

include: _spf.mail.hostinger.com
include: _spf.reach.hostinger.com

Threat-feed evidence

History

Pivot from greenguarddc.org 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: "greenguarddc.org"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.