Skip to content

Hostname

vendome.jp

Last fetched

vendome.jp resolves to 108.157.214.116, announced in 108.157.208.0/21 by AMAZON-02 - Amazon.com, Inc. in SE. vendome.jp 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 · vendome.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/vendome.jp

Resolution chain

IPv6 resolution

No AAAA record for vendome.jp is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
vendome yamada
Contact emails
system1@vendome.co.jp

Subdomains

Subdomain
bridal.vendome.jp
ec2-ins-stage.vendome.jp
new.vendome.jp
old.vendome.jp
qjjgra.vendome.jp
stage.vendome.jp
stg-zcom.vendome.jp
wl-attokyo-prd.vendome.jp
wp.vendome.jp
wpstg.vendome.jp
www.vendome.jp
zcom.vendome.jp

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

  • ns-279.awsdns-34.com
  • ns-718.awsdns-25.net
  • 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
  • ns-1199.awsdns-21.org
  • ns-1641.awsdns-13.co.uk

MX records

  • vyc-gate1.vendome.co.jp

SPF policy

  • mx: vendome.jp
  • include: spf.satorimail.net
  • ip: 122.219.47.50
  • ip: 150.95.57.130
  • ip: 150.95.57.26
  • ip: 150.95.57.37

Threat-feed evidence

History

Related pages

Pivot from vendome.jp 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: "vendome.jp"})-[: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.