Skip to content

Hostname

glitter-cafe.com

Last fetched

glitter-cafe.com resolves to 133.125.69.138, announced in 133.125.0.0/16 by SAKURA-A - SAKURA Internet Inc. in JP. glitter-cafe.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 · glitter-cafe.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/glitter-cafe.com

Resolution chain

IPv6 resolution

No AAAA record for glitter-cafe.com is recorded in WhisperGraph.

Attribution

sakura

ORIGIN_AS

WHOIS identity

Registrar
iana:49
Registrant organisation
whois privacy protection service by onamae.com
Contact emails
proxy@whoisprotectservice.com

Subdomains

Subdomain
mail.glitter-cafe.com
ns1.glitter-cafe.com
ns2.glitter-cafe.com
shop.glitter-cafe.com
www.glitter-cafe.com

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.glitter-cafe.com
  • ns2.glitter-cafe.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

  • mail.glitter-cafe.com

SPF policy

  • ip: 133.125.69.128/28
  • a: glitter-cafe.com
  • mx: glitter-cafe.com
  • a: bike-hoken.jp
  • ip: 153.127.142.76

Threat-feed evidence

History

Related pages

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