Skip to content

Hostname

frogfoot.com

Last fetched

frogfoot.com resolves to 196.1.56.26, announced in 196.1.56.0/21 by Frogfoot Networks - Frogfoot Networks in ZA. frogfoot.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 · frogfoot.comRouting diversity1.5/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/frogfoot.com

Resolution chain

IPv6 resolution

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

Attribution

frogfoot

ORIGIN_AS

WHOIS identity

Registrar
iana:69
Contact emails
abz@frogfoot.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1.frogfoot.net
  • ns2.frogfoot.net
  • ns3.frogfoot.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

MX records

  • frogfoot-com.mail.protection.outlook.com
  • za-smtp-inbound-1.mimecast.co.za
  • za-smtp-inbound-2.mimecast.co.za

SPF policy

  • ip: 41.85.0.0/17
  • mx: frogfoot.com
  • include: za._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • a: sand.frogfoot.net
  • ip: 196.1.60.20
  • ip: 41.206.192.78
  • ip: 41.206.192.99
  • ip: 41.206.193.88
  • ip: 41.206.209.148
  • ip: 41.206.209.200
  • ip: 41.85.15.53
  • ip: 41.85.15.54

Threat-feed evidence

History

Related pages

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