Skip to content

Hostname

connect.syslinq.co

Last fetched

connect.syslinq.co resolves to 4 IPv4 addresses operated by AS20940 in BE.

Nutrition Label

WHISPER CANON · connect.syslinq.coRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint0.0/10canon.whisper.security/host/connect.syslinq.co

Resolution chain

connect.syslinq.co resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
104.117.77.193104.117.77.0/24AS20940—BE
104.117.77.193104.117.77.0/24AS20940—BE
104.117.77.194104.117.77.0/24AS20940—BE
104.117.77.194104.117.77.0/24AS20940—BE
2.16.20.482.16.20.0/24AS12389—RU
2.16.20.732.16.20.0/24AS12389—RU

WHOIS identity

No WHOIS records are currently associated with connect.syslinq.co in WhisperGraph.

Subdomains

2 observed subdomains of connect.syslinq.co.

Subdomain
cloud1.connect.syslinq.co

Showing 1 of 2. View all subdomains →

Threat posture

History

Related pages

Pivot deeper into the graph from connect.syslinq.co.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "connect.syslinq.co"})-[: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 20

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