Skip to content

Hostname

mascom.rs

Last fetched

mascom.rs resolves to 79.175.68.47, announced in 79.175.68.0/23 by ORIONTELEKOM-AS - Drustvo za telekomunikacije Orion telekom doo Beograd-Zemun in RS. mascom.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 · mascom.rsRouting diversity1.5/10Peering density7.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/mascom.rs

Resolution chain

IPv6 resolution

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

Attribution

drustvo za telekomunikacije orion telekom doo beograd zemun

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mascom.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
autoconfig.mascom.rs
autodiscover.mascom.rs
com.mascom.rs
cpanel.mascom.rs
cpcalendars.mascom.rs
cpcontacts.mascom.rs
mail.mascom.rs
mascomstore.mascom.rs
net.mascom.rs
rs.mascom.rs
staging.mascom.rs
webdisk.mascom.rs

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

Mail and authentication

Nameservers

  • alina.ns.cloudflare.com
  • coby.ns.cloudflare.com
  • ns1.netcom.rs
  • ns2.netcom.rs
  • ns3.netcom.rs
  • ns4.netcom.rs

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
  • ip: 79.175.68.3
  • ip: 79.175.68.79

Threat-feed evidence

History

Related pages

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