Hostname
biolegend.com
Last fetched
biolegend.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
biolegend.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 |
|---|---|---|---|---|
| 104.18.20.23 | 104.18.16.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 104.18.21.23 | 104.18.16.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:146
- Organization
- ******** ******** (see notes section below on how to view unmasked data)
- Contact emails
Subdomains
30 observed subdomains of biolegend.com.
Showing 25 of 30. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from biolegend.com in the public web crawl.
800 sites link to this hostname.
Threat posture
History
Mail and authentication
SPF policy
15 SPF mechanisms authorising senders for biolegend.com.
| Mechanism | Target |
|---|---|
| SPF_EXISTS | %{i}._spf.mta.salesforce.com |
| SPF_INCLUDE | aspmx.pardot.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.zohomail360.com |
| SPF_IP | 12.35.196.192/26 |
| SPF_IP | 12.97.44.208/28 |
| SPF_IP | 173.196.211.176/29 |
| SPF_IP | 173.46.145.40 |
| SPF_IP | 193.148.23.148/30 |
| SPF_IP | 208.86.168.7/32 |
| SPF_IP | 213.121.199.74 |
| SPF_IP | 67.129.151.12/32 |
| SPF_IP | 67.231.156.168 |
| SPF_MX | biolegend.com |
Related pages
Pivot deeper into the graph from biolegend.com.
- IP · 104.18.20.23
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:146
- Country · CA
- Email · ********@*****.***
- TLD · .com
- Browse hostnames · bi…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "biolegend.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.