okwave.co.jp


Not observed on urlscan.io


General Info

Geo Seattle, Washington, United States (US) —
AS AS16509 - AMAZON-02, US
Note: An IP might be announced by multiple ASs. This is not shown.
Registrar ARIN
Route 13.225.80.0/21 (Route of ASN)
PTR server-13-225-87-93.fra2.r.cloudfront.net(PTR record of primary IP)
IPv4 13.225.87.93  13.225.87.119  13.225.87.106  13.225.87.124 

Live Screenshot Hover to expand

No direct hits
Nothing is hosted on this domain

No incoming hits
Nothing talked to this domain

DNS recordsRetrieved via DNS ANY query

A 13.225.87.119 (TTL: 59)
A 13.225.87.93 (TTL: 59)
A 13.225.87.106 (TTL: 59)
A 13.225.87.124 (TTL: 59)
MX okwave-co-jp.mail.protection.outlook.com
NS ns-1039.awsdns-01.org
NS ns-1571.awsdns-04.co.uk
NS ns-37.awsdns-04.com
NS ns-542.awsdns-03.net
TXT pardot663603=c26db08a8226659a37d4f854d6fd61d2ffeffb8498d870abc8de69670206922c
TXT v=spf1 include:spf.okwave.co.jp ~all
SOA ns-542.awsdns-03.net
hostmaster: awsdns-hostmaster.amazon.com / serial: 1 / refresh: 7200 / retry: 900 / expire: 1209600 / minttl: 86400 /

WHOIS for okwave.co.jp

[ JPRS database provides information on network administration. Its use is    ]
[ restricted to network administration purposes. For further information,     ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e'     ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'.                 ]

Domain Information:
a. [Domain Name]                OKWAVE.CO.JP
g. [Organization]               OKWAVE
l. [Organization Type]          Ltd.
m. [Administrative Contact]     KK61883JP
n. [Technical Contact]          AG3600JP
p. [Name Server]                ns-1039.awsdns-01.org
p. [Name Server]                ns-542.awsdns-03.net
p. [Name Server]                ns-1571.awsdns-04.co.uk
p. [Name Server]                ns-37.awsdns-04.com
s. [Signing Key]                
[State]                         Connected (2020/09/30)
[Registered Date]               2005/09/30
[Connected Date]                2005/10/03
[Last Update]                   2019/10/16 12:00:05 (JST)

Debug — Elasticsearch took 41ms + 29ms