Skip to content

Hostname

yuki-lab.com

Last fetched

yuki-lab.com resolves to 13.215.239.219, announced in 13.214.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SG. yuki-lab.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 · yuki-lab.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/yuki-lab.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
a41d5173cc824d2fbec79014a99416db.protect@withheldforprivacy.com, privacy@whoisprivacyprotection.info

Subdomains

Subdomain
4137game.yuki-lab.com
battleship.yuki-lab.com
birthday.yuki-lab.com
chess.yuki-lab.com
count.yuki-lab.com
encode-url.yuki-lab.com
igo.yuki-lab.com
jumping.yuki-lab.com
mahjong.yuki-lab.com
neurodivergent.yuki-lab.com
number.yuki-lab.com
pinball.yuki-lab.com

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

  • alina.ns.cloudflare.com
  • mcgrory.ns.cloudflare.com

MX records

  • mx1.privateemail.com
  • mx2.privateemail.com
  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com

SPF policy

  • include: spf.efwd.registrar-servers.com

Threat-feed evidence

History

Related pages

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