Skip to content

Hostname

sailsquare.com

Last fetched

sailsquare.com resolves to 15.160.107.105, announced in 15.160.0.0/16 by AMAZON-02 - Amazon.com, Inc. in IT. sailsquare.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 · sailsquare.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/sailsquare.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:85
Registrant organisation
riccardo boatti
Contact emails
riccardo.boatti@gmail.com

Subdomains

Subdomain
app.sailsquare.com
blog.sailsquare.com
de.sailsquare.com
es.sailsquare.com
fr.sailsquare.com
help.sailsquare.com
it.sailsquare.com
shipyard.sailsquare.com
www.sailsquare.com
yacht.sailsquare.com
yachts.sailsquare.com
yacth.sailsquare.com

Showing 12 of 29. View all subdomains →

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

  • ns-481.awsdns-60.com
  • ns-579.awsdns-08.net
  • ns-1238.awsdns-26.org
  • ns-1711.awsdns-21.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: _spf.mlsend.com
  • include: mail.zendesk.com
  • include: _spf.mailersend.net
  • include: servers.mcsv.net
  • include: eu.mailgun.org

Threat-feed evidence

History

Related pages

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