Skip to content

Hostname

oblaki.com

Last fetched

oblaki.com resolves to 104.21.8.146, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. oblaki.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 · oblaki.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/oblaki.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:48
Registrant organisation
dns register
Contact emails
dsnregister@netguard.bg, webproxy@whoisprotection.domains, mitko@mbal.net

Subdomains

Subdomain
autodiscover.oblaki.com
cpanel.oblaki.com
cpcalendars.oblaki.com
cpcontacts.oblaki.com
d241e34d8ebc.oblaki.com
mail.oblaki.com
webdisk.oblaki.com
webmail.oblaki.com
www.oblaki.com

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

  • blakely.ns.cloudflare.com
  • cash.ns.cloudflare.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

  • _dc-mx.d241e34d8ebc.oblaki.com

SPF policy

  • include: server24.spf.superhosting.bg
  • include: smtp-out.spf.superhosting.bg
  • a: oblaki.com
  • mx: oblaki.com
  • ip: 217.174.156.101

Threat-feed evidence

History

Related pages

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