Skip to content

Hostname

kudeko.com

Last fetched

kudeko.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. kudeko.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 · kudeko.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/kudeko.com

Resolution chain

No IPv4 resolution is recorded for kudeko.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:3853
Contact emails
m18692150340@163.com, 91d7ba7592e26922590ee6f1d0870d5d-1778201@contact.gandi.net, 46fdba11a55ef27808d62554da8c41d35368c041bad2b863b23789388068fdf9@kudeko.com.whoisproxy.org, 9ee0026075ea1bedeec1a517be11473af3f5468527bc9fe30b4af54352cec425@kudeko.com.whoisproxy.org, a85e14c910f2da630f968eb8b7703b6797827f8ee24b4f1841576d6f53568d53@kudeko.com.whoisproxy.org

Subdomains

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns1.grupoloading.com
  • ns2.grupoloading.com
  • ns3.grupoloading.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
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: _spf.loading.es

Threat-feed evidence

History

Related pages

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