Skip to content

Hostname

greencolumnblog.com

Last fetched

greencolumnblog.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. greencolumnblog.com 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

WHISPER CANON · greencolumnblog.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/greencolumnblog.com

Resolution chain

No IPv4 resolution is recorded for greencolumnblog.com in WhisperGraph.

IPv6 resolution

No AAAA record for greencolumnblog.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of greencolumnblog.com owner
Contact emails
067c48b6-8f2d-40ce-baaa-5e6ce0e149f2@identity-protect.org, 0f3daf04-cc10-43d0-8a67-659f9c8f5875@identity-protect.org, 36c82ec2-4e13-4cc6-8b9e-c7e109486c11@identity-protect.org, 6ce1821e-c028-45b9-baed-ef726c966342@identity-protect.org, d4acff98-3bb1-4109-8007-c06ecfd7ead3@identity-protect.org, db9e0a35-cb36-4672-bf3a-2338654a1918@identity-protect.org, ea4825e9-3822-428b-9928-42fafbc24439@identity-protect.org

Subdomains

Subdomain
ob.greencolumnblog.com
obs.greencolumnblog.com
obseu.greencolumnblog.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-328.awsdns-41.com
  • ns-881.awsdns-46.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1260.awsdns-29.org
  • ns-1916.awsdns-47.co.uk

Threat-feed evidence

History

Related pages

Pivot from greencolumnblog.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: "greencolumnblog.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 20

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