Skip to content

Hostname

glock.us

Last fetched

glock.us resolves to 69.20.68.216, announced in 69.20.0.0/17 by RACKSPACE - Rackspace Hosting in US. glock.us 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 · glock.usRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/glock.us

Resolution chain

IPv6 resolution

No AAAA record for glock.us is recorded in WhisperGraph.

Attribution

rackspace

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
miro vran
Contact emails
webmaster@glock.us

Subdomains

Subdomain
19x.glock.us
auth-dev.glock.us
auth-stg.glock.us
autodiscover.glock.us
dealermaterials.glock.us
dealers-crm.glock.us
designer.glock.us
donations.glock.us
em4501.glock.us
em8797.glock.us
enrollments-api.glock.us
enrollments.glock.us

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

  • ns43.domaincontrol.com
  • ns44.domaincontrol.com
  • 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

MX records

  • glock-us.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • mx: glock.us
  • include: em4501.glock.us
  • include: em8797.glock.us
  • ip: 47.48.203.7
  • ip: 62.218.230.164
  • ip: 62.218.239.238
  • ip: 65.106.251.210
  • ip: 65.106.251.221
  • ip: 66.104.152.197
  • ip: 80.120.253.118
  • ip: 80.120.253.119

Threat-feed evidence

History

Related pages

Pivot from glock.us 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: "glock.us"})-[: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.