Hostname
is-bang.com
Last fetched
is-bang.com resolves to 4 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in JP. WHOIS lists iana:49 as the registrar.
Nutrition Label
Resolution chain
is-bang.com resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.114.245.206 | 13.112.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 13.159.244.66 | 13.158.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 54.64.115.9 | 54.64.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 54.64.133.122 | 54.64.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
WHOIS identity
- Registrar
- iana:49
- Organization
- songai hoken minaoshi honpo co.,ltd.
- Contact emails
Subdomains
5 observed subdomains of is-bang.com.
Web-graph footprint
Distinct hostnames that link to or from is-bang.com in the public web crawl.
17 sites link to this hostname.
2 sites linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
14 SPF mechanisms authorising senders for is-bang.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.webcrew-dev.smtps.jp |
| SPF_INCLUDE | spf.webcrew-inc.smtps.jp |
| SPF_IP | 18.176.3.51 |
| SPF_IP | 210.152.207.207 |
| SPF_IP | 210.152.207.208 |
| SPF_IP | 210.152.207.209 |
| SPF_IP | 210.152.235.22 |
| SPF_IP | 210.152.235.23 |
| SPF_IP | 210.152.235.24/29 |
| SPF_IP | 35.73.122.155 |
| SPF_IP | 35.73.136.224 |
| SPF_IP | 35.77.169.51 |
| SPF_IP | 52.195.74.138 |
| SPF_IP | 54.150.66.76 |
Related pages
Pivot deeper into the graph from is-bang.com.
- IP · 13.114.245.206
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:49
- Country · JP
- Email · domain@webcrew.co.jp
- TLD · .com
- Browse hostnames · is…
- 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: "is-bang.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.