Skip to content

Hostname

ty.com

Last fetched

ty.com resolves to 172.169.51.95, announced in 172.160.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. ty.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 · ty.comRouting diversity2.4/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/ty.com

Resolution chain

IPv6 resolution

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

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

Registrar
iana:886
Registrant organisation
j. bogacki
Contact emails
dataprotected@maskeddetails.com, domainmgr@tymail.com, jbogacki@tymail.com, noreply@data-protected.net

Subdomains

Subdomain
autodiscover.ty.com
avayaconfig.ty.com
avayasip.ty.com
beanie-babies.ty.com
campaign.ty.com
cdn.ty.com
cloud.ty.com
devlar1.ty.com
email.ty.com
ex2010.ty.com
ex2016.ty.com
ex2016b.ty.com

Showing 12 of 33. 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

  • ns1131.dns.dyn.com
  • ns2154.dns.dyn.com
  • ns3143.dns.dyn.com
  • ns4155.dns.dyn.com
  • ns1.mydyndns.org

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 64.238.211.94/32
  • include: cust-spf.exacttarget.com
  • include: spfhost.messageprovider.com
  • include: eu._netblocks.mimecast.com
  • include: us._netblocks.mimecast.com
  • include: usb._netblocks.mimecast.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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