Skip to content

Hostname

theforce.co.za

Last fetched

theforce.co.za resolves to 102.211.204.40, announced in 102.211.204.0/22 by Absolute Hosting (Pty) Ltd - Absolute Hosting (Pty) Ltd in ZA. theforce.co.za 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 · theforce.co.zaRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/theforce.co.za

Resolution chain

IPv6 resolution

No AAAA record for theforce.co.za is recorded in WhisperGraph.

Attribution

absolute

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for theforce.co.za. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
ftp.theforce.co.za
mail.theforce.co.za
ns1.theforce.co.za
ns2.theforce.co.za
ns3.theforce.co.za
ns4.theforce.co.za
www.theforce.co.za

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • ns1.mydnscloud.com
  • ns2.mydnscloud.com
  • ns3.mydnscloud.com
  • ns4.mydnscloud.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

  • theforce.co.za

SPF policy

  • a: theforce.co.za
  • mx: theforce.co.za
  • ip: 102.211.204.40

Threat-feed evidence

History

Related pages

Pivot from theforce.co.za 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: "theforce.co.za"})-[: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.