Hostname
civic.jp
Last fetched
civic.jp resolves to 18.164.124.103, announced in 18.164.124.0/22 by AMAZON-02 - Amazon.com, Inc. in US. civic.jp is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 18.164.124.103
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.124.3
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.124.59
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.124.67
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.175.64.24
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 3.175.64.79
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 3.175.64.80
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 3.175.64.92
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
IPv6 resolution
No AAAA record for civic.jp is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrant organisation
- hitachi city science,culture and information foundation
- Contact emails
- civic@civic.jp, domain@ictop.jp, domains@heartbeats.jp, support@unicast.ne.jp
Subdomains
| Subdomain |
|---|
| mail.civic.jp |
| ns.civic.jp |
| www.civic.jp |
Showing 3 of 3 subdomains (3 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
Mail and authentication
Nameservers
- ns-129.awsdns-16.com
- ns-989.awsdns-59.net
- ns-1055.awsdns-03.org
- ns-1618.awsdns-10.co.uk
MX records
- mail.civic.jp
SPF policy
- ip: 210.140.57.203/32
- include: amazonses.com
- a: civic.jp
- mx: civic.jp
Threat-feed evidence
History
Related pages
Pivot from civic.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: "civic.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.