Hostname
secureconduit.net
Last fetched
secureconduit.net resolves to 1 IPv4 address operated by UNIFIEDLAYER-AS-1 - Unified Layer in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
secureconduit.net resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 198.1.79.120 | 198.1.64.0/18 | AS46606 | UNIFIEDLAYER-AS-1 - Unified Layer | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- chris sanders
- Contact emails
- domains@ventanex.com
- 12a20f8cf31d4c5883a75e1237d2ef11.protect@whoisguard.com
- 1d411c27-921c-4dd8-9e93-9be7e5545d88@identity-protect.org
- 40fa0d41-8b54-4b9c-b9ab-aebc97e41da6@identity-protect.org
- 63aaf592-a013-46ba-8d0a-4f0b9d999ed9@identity-protect.org
- 8692a996-8bf8-4ef2-82ab-00a01187c8b0@identity-protect.org
- f9ff147f-4ccc-49c1-98a1-b3975f3c5f38@identity-protect.org
- ff747727-64a4-4ad5-978b-ea4ea631ea57@identity-protect.org
- owner-11229043@secureconduit.net.whoisprivacyservice.org
Subdomains
106 observed subdomains of secureconduit.net.
Showing 25 of 106. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from secureconduit.net in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for secureconduit.net.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | sendgrid.net |
Related pages
Pivot deeper into the graph from secureconduit.net.
- IP · 198.1.79.120
- ASN · AS46606UNIFIEDLAYER-AS-1 - Unified Layer
- Registrar · iana:468
- Country · US
- Email · domains@ventanex.com
- TLD · .net
- Browse hostnames · se…
- 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: "secureconduit.net"})-[: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.