Skip to content

Hostname

yt2save.com

Last fetched

yt2save.com resolves to 51.38.206.129, announced in 51.38.0.0/16 by OVH - OVH SAS in FR. yt2save.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 · yt2save.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/yt2save.com

Resolution chain

IPv6 resolution

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

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1601
Registrant organisation
guzel hosting musteri
Contact emails
4628fb6953c64c128eeb2eb73b7e6ce5.protect@withheldforprivacy.com, bildirim@guzel.net.tr

Subdomains

Subdomain
mail.yt2save.com
www.yt2save.com

Showing 2 of 2 subdomains (2 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

  • ns1.guzelhosting.com
  • ns11.guzelhosting.com
  • ns12.guzelhosting.com
  • ns2.guzelhosting.com
  • 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

  • yt2save.com

SPF policy

  • include: relay.guzelhosting.com
  • a: yt2save.com
  • mx: yt2save.com

Threat-feed evidence

History

Related pages

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