Skip to content

Hostname

akorlar.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:895
Registrant organisation
contact privacy inc. customer 7151571251
Contact emails
goksel@kervanci.com, mevlut_yildiz@mynet.com, yilmaz@gmail.com

Subdomains

Subdomain
220-server.akorlar.com
cpanel.akorlar.com
cpcalendars.akorlar.com
cpcontacts.akorlar.com
mail.akorlar.com
ns1.akorlar.com
ns2.akorlar.com
server.akorlar.com
webdisk.akorlar.com
webmail.akorlar.com
www.akorlar.com

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

Mail and authentication

Nameservers

  • ines.ns.cloudflare.com
  • will.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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