Hostname
312defense.com
Last fetched
312defense.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in CA. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
312defense.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 |
|---|---|---|---|---|
| 18.239.6.25 | 18.239.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 18.239.6.6 | 18.239.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 18.239.6.68 | 18.239.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 18.239.6.95 | 18.239.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 18.244.60.17 | 18.244.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.244.60.20 | 18.244.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.244.60.9 | 18.244.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.244.60.97 | 18.244.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
WHOIS identity
- Registrar
- iana:146
- Organization
- david olshansky
- Contact emails
Subdomains
5 observed subdomains of 312defense.com.
Web-graph footprint
Distinct hostnames that link to or from 312defense.com in the public web crawl.
9 sites link to this hostname.
11 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for 312defense.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_IP | 166.62.85.30 |
Related pages
Pivot deeper into the graph from 312defense.com.
- IP · 18.239.6.25
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:146
- Country · CA
- Email · david@312defense.com
- TLD · .com
- Browse hostnames · 31…
- 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: "312defense.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.