Skip to content

Hostname

pin.ly

Last fetched

pin.ly resolves to 13.89.57.7, announced in 13.64.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. pin.ly 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 · pin.lyRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/pin.ly

Resolution chain

IPv6 resolution

No AAAA record for pin.ly is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:libyan spider network (int)
Registrant organisation
carmel software
Contact emails
stephenroth@gmail.com

Subdomains

Subdomain
mail.pin.ly

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • ns1.libyanspider.com
  • ns2.libyanspider.com
  • ns3.libyanspider.com
  • ns4.libyanspider.com

MX records

  • mail.pin.ly

Threat-feed evidence

History

Related pages

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