Skip to content

Hostname

akaiideas.com

Last fetched

akaiideas.com resolves to 144.76.107.101, announced in 144.78.160.0/22 by HETZNER-AS - Hetzner Online GmbH in DE. akaiideas.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:31 GMT
Last seen on a feed
Tue, 22 Sep 2026 19:47:35 GMT

Nutrition Label

WHISPER CANON · akaiideas.comRouting diversity2.4/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/akaiideas.com

Resolution chain

IPv6 resolution

No AAAA record for akaiideas.com is recorded in WhisperGraph.

Attribution

Google

cloud · MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1647
Registrant organisation
domain admin
Contact emails
contact@privacyprotect.org

Subdomains

Subdomain
access.akaiideas.com
connect.akaiideas.com
cpanel.akaiideas.com
cpcalendars.akaiideas.com
cpcontacts.akaiideas.com
mail.akaiideas.com
test.akaiideas.com
vpn1.akaiideas.com
webdisk.akaiideas.com
webmail.akaiideas.com
webvpn.akaiideas.com
whm.akaiideas.com

Showing 12 of 14. View all subdomains →

Mail and authentication

Nameservers

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net
  • n1.hostnext.net
  • n2.hostnext.net
  • ns1.hostnext.net
  • ns2.hostnext.net

MX records

  • akaiideas.com

SPF policy

  • a: akaiideas.com
  • mx: akaiideas.com
  • include: relay.mailchannels.net
  • ip: 144.76.107.101

Threat-feed evidence

History

Related pages

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