Hostname
bradycorp.com
Last fetched
bradycorp.com resolves to 2 IPv4 addresses operated by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US.
Nutrition Label
Resolution chain
bradycorp.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 20.80.75.138 | 20.64.0.0/10 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | US |
| 204.74.99.200 | 204.74.99.0/24 | AS19905 | SECURITYSERVICES - Vercara, LLC | US |
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 bradycorp.com in the public web crawl.
Threat posture
History
Mail and authentication
MX records
SPF policy
29 SPF mechanisms authorising senders for bradycorp.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 1681749.spf07.hubspotemail.net |
| SPF_INCLUDE | _spf.atlassian.net |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | spfa.cpmails.com |
| SPF_IP | 104.197.65.145/32 |
| SPF_IP | 12.69.60.157/32 |
| SPF_IP | 142.0.172.25/32 |
| SPF_IP | 158.228.129.79/32 |
| SPF_IP | 158.228.200.70/32 |
| SPF_IP | 162.251.209.5/32 |
| SPF_IP | 167.89.70.61/32 |
| SPF_IP | 185.2.54.136/32 |
| SPF_IP | 185.92.38.235/32 |
| SPF_IP | 199.59.200.201/32 |
| SPF_IP | 205.220.168.164 |
| SPF_IP | 205.220.180.164 |
| SPF_IP | 209.177.165.161/32 |
| SPF_IP | 213.171.192.249/32 |
| SPF_IP | 213.171.193.245/32 |
| SPF_IP | 213.41.42.80/28 |
| SPF_IP | 31.172.232.198/32 |
| SPF_IP | 34.58.215.46/32 |
| SPF_IP | 5.226.2.176/28 |
| SPF_IP | 54.69.206.159/32 |
| SPF_IP | 64.73.120.224/27 |
| SPF_IP | 74.201.71.36/32 |
| SPF_IP | 80.237.132.81/32 |
| SPF_IP | 81.171.183.94/32 |
Related pages
Pivot deeper into the graph from bradycorp.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bradycorp.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.