Skip to content

Hostname

gateless.com

Last fetched

gateless.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. gateless.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · gateless.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/gateless.com

Resolution chain

No IPv4 resolution is recorded for gateless.com in WhisperGraph.

IPv6 resolution

No AAAA record for gateless.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of gateless.com owner
Contact emails
gateless.com@domainsbyproxy.com, ian@dotcomagency.com, 060c98d7-b2b1-4390-8189-f265547b58d8@identity-protect.org, 0e6bb51c-d3a4-48fd-a9e3-cf7c8020021d@identity-protect.org, 2a1da5c5-a9a4-4a1e-b982-c874bd0fb066@identity-protect.org, e3b3762d-a248-4e8f-8438-e64444c2ce90@identity-protect.org, f9985b85-0703-4f90-8df9-783f9e6e6690@identity-protect.org, fc6fffbf-7346-41ab-b7bd-4a6fa4de85f1@identity-protect.org, owner-3822847@gateless.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-334.awsdns-41.com
  • ns-655.awsdns-17.net
  • ns-1512.awsdns-61.org
  • ns-1948.awsdns-51.co.uk

MX records

  • gateless-com.mail.protection.outlook.com

SPF policy

  • ip: 142.0.160.0/20
  • ip: 162.247.216.0/22
  • include: us._netblocks.mimecast.com
  • include: mktomail.com
  • include: spf.protection.outlook.com
  • include: partnerxchangespf.smtp.com
  • ip: 40.78.134.92

Threat-feed evidence

History

Related pages

Pivot from gateless.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "gateless.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.