Skip to content

Hostname

glider.ink

Last fetched

glider.ink resolves to 188.226.245.148, announced in 188.226.128.0/17 by DIGITALOCEAN-ASN - DigitalOcean, LLC in NL. glider.ink 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 · glider.inkRouting diversity1.5/10Peering density7.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/glider.ink

Resolution chain

IPv6 resolution

No AAAA record for glider.ink is recorded in WhisperGraph.

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
pawel chojnacki
Contact emails
5x1xkjh6vifvzas2ml8e@n.o-w-o.info, aqnulu0oat3itv3oypws@u.o-w-o.info, cyix54brgmxzacxa07sy@r.o-w-o.info, elawsv024ijg11vq4n9b@t.o-w-o.info

Subdomains

Subdomain
blog.glider.ink
new.glider.ink
wiki.glider.ink
www.glider.ink

Showing 4 of 4 subdomains (4 per page).

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • dns109.ovh.net
  • ns109.ovh.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mxext1.mailbox.org
  • mxext2.mailbox.org
  • mxext3.mailbox.org
  • mxext4.mailbox.org

SPF policy

  • include: mx.ovh.com
  • include: mailbox.org

Threat-feed evidence

History

Related pages

Pivot from glider.ink 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: "glider.ink"})-[: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.