Skip to content

Hostname

wearelightforce.com

Last fetched

wearelightforce.com resolves to 107.21.92.82, announced in 107.21.64.0/18 by AMAZON-AES - Amazon.com, Inc. in US. wearelightforce.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 · wearelightforce.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/wearelightforce.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of wearelightforce.com owner
Contact emails
00c84ea2-7015-4a4a-b0ee-d6f74a6bf5d2@identity-protect.org, 7da07ead-cc03-4f1b-9d53-81bdb200f16b@identity-protect.org, af492086-a7e9-4bf5-a05d-16b3a09ebd1e@identity-protect.org, bcbacf69-920d-49b9-9bdf-355d67cfe38b@identity-protect.org, c90483c7-5083-4117-bd98-4a93fccaf599@identity-protect.org, fda65f04-1689-499d-bdc8-10d2530d2de0@identity-protect.org, owner-3765045@wearelightforce.com.whoisprivacyservice.org

Subdomains

Subdomain
www.wearelightforce.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • ns-122.awsdns-15.com
  • ns-556.awsdns-05.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-1083.awsdns-07.org
  • ns-1714.awsdns-22.co.uk

Threat-feed evidence

History

Related pages

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