Skip to content

Hostname

dickies.jp

Last fetched

dickies.jp resolves to 157.7.174.95, announced in 157.7.128.0/17 by GMO-I-R1 - GMO Internet, Inc. in JP. dickies.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 · dickies.jpRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.2/10canon.whisper.security/host/dickies.jp

Resolution chain

IPv6 resolution

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

Attribution

gmo

ORIGIN_AS

WHOIS identity

Registrant organisation
vf (japan)
Contact emails
domainmanager@dickies-japan.com, vfc_domain_admins@vfc.com, yukie_fujimoto@vfc.com

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.101domain.com
  • ns2.101domain.com
  • ns5.101domain.com
  • ns1.vfc.com
  • a1-250.akam.net
  • a12-64.akam.net
  • a13-67.akam.net
  • a2-65.akam.net
  • a24-64.akam.net
  • a5-66.akam.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

MX records

  • reply.s51.exacttarget.com
  • mx.dickies.jp

SPF policy

  • ip: 149.72.34.16/32
  • ip: 124.109.181.7/32
  • include: amazonses.com
  • include: cust-spf.exacttarget.com
  • include: spf.ecbeing.co.jp
  • a: dickies.jp
  • mx: dickies.jp
  • include: smp.ne.jp
  • include: _spf.shared-server.net
  • ip: 1.33.180.29

Threat-feed evidence

History

Related pages

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