Hostname
blusensor.com
Last fetched
blusensor.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:1408 as the registrar.
Nutrition Label
Resolution chain
blusensor.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.226.94.109 | 13.226.94.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.226.94.13 | 13.226.94.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.226.94.21 | 13.226.94.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.226.94.61 | 13.226.94.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 143.204.204.100 | 143.204.204.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 143.204.204.28 | 143.204.204.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 143.204.204.35 | 143.204.204.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 143.204.204.69 | 143.204.204.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:1408
- Organization
- almendo technologies
- Contact emails
Subdomains
8 observed subdomains of blusensor.com.
Web-graph footprint
Distinct hostnames that link to or from blusensor.com in the public web crawl.
9 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for blusensor.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | servers.mcsv.net |
Related pages
Pivot deeper into the graph from blusensor.com.
- IP · 13.226.94.109
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:1408
- Country · US
- Email · office@almendo.com
- TLD · .com
- Browse hostnames · bl…
- 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: "blusensor.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.