Skip to content

Hostname

skytel.ge

Last fetched

skytel.ge resolves to 4.182.110.144, announced in 4.176.0.0/12 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in DE. skytel.ge 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 · skytel.geRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/skytel.ge

Resolution chain

IPv6 resolution

No AAAA record for skytel.ge is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for skytel.ge. 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
about.skytel.ge
any.skytel.ge
apps.skytel.ge
autodiscover.skytel.ge
bf.skytel.ge
business.skytel.ge
cc.skytel.ge
dev.skytel.ge
drive.skytel.ge
epg.skytel.ge
install.skytel.ge
ion.skytel.ge

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

  • ns0.skytel.ge
  • ns1.skytel.ge
  • ns2.skytel.ge

MX records

  • skytel-ge.mail.protection.outlook.com
  • mx01.skytel.ge

SPF policy

  • include: spf.protection.outlook.com
  • a: skytel.ge
  • mx: skytel.ge

Threat-feed evidence

History

Related pages

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