Skip to content

Hostname

frecious.jp

Last fetched

frecious.jp resolves to 103.5.177.133, announced in 103.5.176.0/22 by WHOSNEXT - Who's Next in JP. frecious.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 · frecious.jpRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint5.2/10canon.whisper.security/host/frecious.jp

Resolution chain

IPv6 resolution

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

Attribution

who next

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrant organisation
bet_inc
Contact emails
info@xserver.co.jp, support@xserver.ne.jp

Subdomains

Subdomain
a8cv.frecious.jp
affitown.frecious.jp
every.frecious.jp
image.frecious.jp
mail.frecious.jp
order.frecious.jp
sagidesu-hirakuna.frecious.jp
sf.frecious.jp
v.frecious.jp
wm.frecious.jp
www.frecious.jp

Showing 11 of 11 subdomains (11 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.xserver.jp
  • ns2.xserver.jp
  • ns3.xserver.jp
  • ns4.xserver.jp
  • ns5.xserver.jp

MX records

  • frecious.jp

SPF policy

  • ip: 103.5.176.0/22
  • include: _spf.google.com
  • include: spf.spcloud.jp
  • include: spf.tricorn.net

Threat-feed evidence

History

Related pages

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