Skip to content

Hostname

yettel.rs

Last fetched

yettel.rs resolves to 217.65.192.22, announced in 217.65.192.0/20 by CETIN_doo_AS - CETIN Ltd. Belgrade in RS. yettel.rs 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 · yettel.rsRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/yettel.rs

Resolution chain

IPv6 resolution

No AAAA record for yettel.rs is recorded in WhisperGraph.

Attribution

cetin belgrade

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for yettel.rs. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
analytics.yettel.rs
api.yettel.rs
apihub.yettel.rs
autodiscover.yettel.rs
cee.yettel.rs
citrix.yettel.rs
cpa.yettel.rs
cpaweb.yettel.rs
developers.yettel.rs
dopunibroj.yettel.rs
dwp.yettel.rs
idprovera-t.yettel.rs

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

  • dinosaur.cetin.rs
  • dns2.cetin.rs
  • ns2.cetin.rs
  • dnssrv1.cloudhosting.rs

MX records

  • yettel-rs.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: _spf-dc12.successfactors.com
  • a: yettel.rs
  • mx: yettel.rs
  • include: spf.yettel.rs

Threat-feed evidence

History

Related pages

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