Skip to content

Hostname

glgresearch.com

Last fetched

glgresearch.com resolves to 107.22.179.180, announced in 107.22.0.0/16 by AMAZON-AES - Amazon.com, Inc. in US. glgresearch.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 · glgresearch.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/glgresearch.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
domainreg@glgroup.com

Subdomains

Subdomain
bcg.glgresearch.com
block-ioc-lists.glgresearch.com
blog-testing.glgresearch.com
blog.glgresearch.com
blog2.glgresearch.com
cf-test.glgresearch.com
cli.glgresearch.com
client-auth.glgresearch.com
cloudflare-testing.glgresearch.com
councils.glgresearch.com
dev.glgresearch.com
email-internal.glgresearch.com

Showing 12 of 54. View all subdomains →

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-148.awsdns-18.com
  • ns-543.awsdns-03.net
  • ns-1329.awsdns-38.org
  • ns-1960.awsdns-53.co.uk

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 38.112.210.0/24
  • ip: 67.202.236.0/24
  • ip: 74.205.239.0/24
  • ip: 218.189.87.241/29
  • ip: 65.91.117.33/27
  • include: _netblocks.mimecast.com
  • include: mktomail.com
  • include: spf.protection.outlook.com
  • ip: 173.227.88.62

Threat-feed evidence

History

Related pages

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