Skip to content

Hostname

zgf.com

Last fetched

zgf.com resolves to 173.249.147.166, announced in 173.249.147.0/24 by VPSDATACENTER - Liquid Web, L.L.C in US. zgf.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 · zgf.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/zgf.com

Resolution chain

IPv6 resolution

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

Attribution

liquid

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
zimmer gunsul frasca architects llp
Contact emails
admin@zgf.com, alta.hamoui@zgf.com, jan.lochridge@zgf.com

Subdomains

Subdomain
autodiscover.zgf.com
dc-fg-1.zgf.com
den-fg-1.zgf.com
email.zgf.com
ems.zgf.com
lax-fg-1.zgf.com
nyc-fg-1.zgf.com
pdx-fg-1.zgf.com
pdx-lab-60f.zgf.com
pdx-remote.zgf.com
pdx-wan2.zgf.com
pki.zgf.com

Showing 12 of 24. 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

Mail and authentication

Nameservers

  • ns11.constellix.com
  • ns21.constellix.com
  • ns31.constellix.com
  • ns41.constellix.net
  • ns51.constellix.net
  • ns61.constellix.net

MX records

  • zgf-com.mail.protection.outlook.com

SPF policy

  • ip: 205.251.168.162/32
  • include: _spf.psm.knowbe4.com
  • include: spf.protection.outlook.com
  • ip: 108.71.255.161
  • ip: 199.10.84.142
  • ip: 207.159.98.18
  • ip: 38.104.124.122
  • ip: 38.104.237.162
  • ip: 38.140.62.138
  • ip: 4.14.140.202
  • ip: 4.15.128.14
  • ip: 50.223.10.26
  • ip: 50.251.232.45
  • ip: 64.16.56.58
  • ip: 69.196.65.115
  • ip: 96.89.108.68
  • ip: 96.91.246.89

Threat-feed evidence

History

Related pages

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