Skip to content

Hostname

bbqs.com

Last fetched

bbqs.com resolves to 16.58.153.124, announced in 16.58.128.0/17 by AMAZON-02 - Amazon.com, Inc. in US. bbqs.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 · bbqs.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint7.4/10canon.whisper.security/host/bbqs.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of bbqs.com owner
Contact emails
bbqs.com@domainsbyproxy.com, duff@bbqs.com, 45362cc9-21a8-48e5-b5dd-b7a383759acf@identity-protect.org, 8ff6dcbd-d8ab-4d86-af69-cdfbcccb1df0@identity-protect.org, 9621a5fb-de8d-4cae-8842-77daf322fb21@identity-protect.org, df896ca4-1499-49fe-83f9-db256a4b4f34@identity-protect.org

Subdomains

Subdomain
www.bbqs.com

Showing 1 of 1 subdomain (1 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

  • ns-8.awsdns-01.com
  • ns-48.awsdns-06.com
  • ns-196.awsdns-24.com
  • ns-600.awsdns-11.net
  • ns-738.awsdns-28.net
  • ns-915.awsdns-50.net
  • ns-1210.awsdns-23.org
  • ns-1311.awsdns-35.org
  • ns-1355.awsdns-41.org
  • ns-1578.awsdns-05.co.uk
  • ns-1690.awsdns-19.co.uk
  • ns-1958.awsdns-52.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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