Skip to content

Hostname

wakefields.co.za

Last fetched

wakefields.co.za resolves to 107.23.64.217, announced in 107.23.0.0/17 by AMAZON-AES - Amazon.com, Inc. in US. wakefields.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 · wakefields.co.zaRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/wakefields.co.za

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:930
Registrant organisation
wakefields real estate (pty)
Contact emails
mikericeman@wakefields.co.za

Subdomains

Subdomain
analytics.wakefields.co.za
ironport.wakefields.co.za
m.wakefields.co.za
mail.wakefields.co.za
mtn-wl001-jhb.wakefields.co.za
old.wakefields.co.za
tracking.wakefields.co.za
www.wakefields.co.za

Showing 8 of 8 subdomains (8 per page).

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

  • 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
  • main.nameserver1.co.za
  • main.nameserver2.co.za
  • main.nameserver3.co.za
  • main.nameserver4.co.za

MX records

  • securemail-mx1.synaq.com
  • securemail-mx2.synaq.com

SPF policy

  • include: _spf.elasticemail.com
  • include: _spf-cloudmail.synaq.com

Threat-feed evidence

History

Related pages

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