Skip to content

Hostname

breakingmuscle.com

Last fetched

breakingmuscle.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in DE.

Nutrition Label

WHISPER CANON · breakingmuscle.comRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/breakingmuscle.com

Resolution chain

breakingmuscle.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
18.245.31.12718.245.30.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
18.245.31.12918.245.30.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
18.245.31.4018.245.30.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
18.245.31.6918.245.30.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
3.171.117.243.171.116.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.117.313.171.116.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.117.363.171.116.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.117.573.171.116.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
65.9.175.10565.9.174.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
65.9.175.1765.9.174.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
65.9.175.6765.9.174.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
65.9.175.8265.9.174.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

Distinct hostnames that link to or from breakingmuscle.com in the public web crawl.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

7 SPF mechanisms authorising senders for breakingmuscle.com.

MechanismTarget
SPF_Abreakingmuscle.com
SPF_Adb1.tgdaily.com
SPF_Arubicon.tgdaily.com
SPF_Aweb1.tgdaily.com
SPF_INCLUDE_spf.google.com
SPF_IP76.75.207.16/28
SPF_MXbreakingmuscle.com

Related pages

Pivot deeper into the graph from breakingmuscle.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "breakingmuscle.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.