Skip to content

Hostname

waikly.com

Last fetched

waikly.com resolves to 103.224.212.111, announced in 103.224.212.0/24 by STEFANSTEVAN - Stefan Stevanovic in AU. waikly.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 · waikly.comRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/waikly.com

Resolution chain

IPv6 resolution

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

Attribution

stefan stevanovic

ORIGIN_AS

WHOIS identity

Registrar
iana:753
Registrant organisation
on behalf of waikly.com owner
Contact emails
3cdm6pchcqigr9e9epbb6qmdoe@domaindiscreet.com, owner-442210@waikly.com.whoisprivacyservice.org, owner-8197053@waikly.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1.abovedomains.com
  • ns2.abovedomains.com
  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com
  • 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

MX records

  • park-mx.above.com
  • mx1-hosting.jellyfish.systems
  • mx2-hosting.jellyfish.systems
  • mx3-hosting.jellyfish.systems

SPF policy

  • a: waikly.com
  • mx: waikly.com
  • include: spf.web-hosting.com
  • ip: 162.213.251.115

Threat-feed evidence

History

Related pages

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