Skip to content

Hostname

linkody.com

Last fetched

linkody.com resolves to 134.122.58.22, announced in 134.122.48.0/20 by DIGITALOCEAN-ASN - DigitalOcean, LLC in NL. linkody.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 · linkody.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/linkody.com

Resolution chain

IPv6 resolution

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

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
franã§ois mommens
Contact emails
mommens@gmail.com, ogaj0tms5b0y0x8ghspi@u.o-w-o.info, 09fcdbb444e7dadf55adac77cdd100ba-1830283@contact.gandi.net, 422b08623b67b1a937eaec6a1e658d7c-1830283@contact.gandi.net, 6371b7cb3f58b406bfbdcdcf153d19cb-1830283@contact.gandi.net, 63af7f19f61ad79250a534cb2b228e71-1830283@contact.gandi.net, b667823d1ce21416567e77292eb9a60c-1830283@contact.gandi.net

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-172-a.gandi.net
  • ns-224-b.gandi.net
  • ns-70-c.gandi.net
  • ns1.gandi.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: _spf.google.com
  • a: linkody.com
  • mx: linkody.com
  • include: sendersrv.com
  • include: mailgun.org

Threat-feed evidence

History

Related pages

Pivot from linkody.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: "linkody.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.