Skip to content

Hostname

performancebeef.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
dallas@farmtilepro.com, 170a5d9d-90b9-417d-934c-8c9533826a54@identity-protect.org, 3811e351-82db-4050-b922-74bc9c259dfc@identity-protect.org, 4e3104fd-1114-4ebf-8fc1-a8445bd3b288@identity-protect.org, 57136b80-59c7-4493-9fa8-1f93504db5a7@identity-protect.org, c1b05c3e-0b67-41fe-b6ac-934c4ae602c2@identity-protect.org, c5e331d9-2647-4393-9090-f03c4b2ff167@identity-protect.org, cce2c70b-d761-4b8c-8e9d-0fc7e2be3f84@identity-protect.org

Subdomains

Mail and authentication

Nameservers

  • ns-5.awsdns-00.com
  • ns-901.awsdns-48.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-1430.awsdns-50.org
  • ns-1749.awsdns-26.co.uk

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: 2048951.spf08.hubspotemail.net

Threat-feed evidence

History

Related pages

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