Hostname
bladeserpent.com
Last fetched
bladeserpent.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in IT. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
bladeserpent.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 |
|---|---|---|---|---|
| 108.138.192.118 | 108.138.192.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 108.138.192.4 | 108.138.192.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 108.138.192.78 | 108.138.192.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 108.138.192.93 | 108.138.192.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 3.164.68.48 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.68.5 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.68.63 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.68.75 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
Subdomains
5 observed subdomains of bladeserpent.com.
Web-graph footprint
Distinct hostnames that link to or from bladeserpent.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
4 SPF mechanisms authorising senders for bladeserpent.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | spf.mandrillapp.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | zcsend.net |
Related pages
Pivot deeper into the graph from bladeserpent.com.
- IP · 108.138.192.118
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:146
- Country · IT
- Email · bladeserpent.com@domainsbyproxy.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: "bladeserpent.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.