Hostname
clover.co.za
Last fetched
clover.co.za resolves to 13.107.213.68, announced in 13.107.3.0/24 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. clover.co.za is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.107.213.68
13.107.3.0/24 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.213.69
13.107.3.0/24 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.226.45
13.107.3.0/24 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Toronto, CA
- 13.107.246.68
13.107.3.0/24 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.246.69
13.107.3.0/24 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.253.45
13.107.3.0/24 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Toronto, CA
- 150.171.109.100
150.174.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Nairobi, KE
- 150.171.109.101
150.174.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Nairobi, KE
- 150.171.109.107
150.174.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
IPv6 resolution
No AAAA record for clover.co.za is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:1api gmbh
- Registrant organisation
- clover s.a. (pty)
- Contact emails
- dns.admin@clover.co.za, it.dns@clover.co.za
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
- ns1-08.azure-dns.com
- ns4-08.azure-dns.info
- ns2-08.azure-dns.net
- ns3-08.azure-dns.org
MX records
- za-smtp-inbound-1.mimecast.co.za
- za-smtp-inbound-2.mimecast.co.za
Threat-feed evidence
History
Related pages
Pivot from clover.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: "clover.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.