nttr.co.jp


Not observed on urlscan.io


General Info

Geo Hirakata, Nagasaki, Japan (JP) —
AS AS2514 - INFOSPHERE NTT PC Communications, Inc., JP
Note: An IP might be announced by multiple ASs. This is not shown.
Registrar APNIC
Route 202.212.0.0/16 (Route of ASN)
PTR st3730.nas811.p-osaka.nttpc.ne.jp(PTR record of primary IP)
IPv4 202.212.8.18 

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 202.212.8.18 (TTL: 899)
MX mta1.nttr.co.jp (Priority: 60)
NS ns.via.or.jp
NS ns1.goo.ne.jp
NS ns2.goo.ne.jp
NS ns.intervia.ad.jp
TXT MS=ms91854436
TXT v=spf1 +ip4:202.217.72.192/27 +ip4:203.138.161.229 +ip4:203.138.122.103 include:aspmx.pardot.com include:nttr.spf.cuenote.jp include:spf001.nttr.co.jp include:spf.protection.outlook.com include:spf.mail.goo.jp include:_spf.salesforce.com ~all
SOA ns1.goo.ne.jp
hostmaster: hostmaster.goo.ne.jp / serial: 238 / refresh: 7200 / retry: 3600 / expire: 3600000 / minttl: 86400 /

WHOIS for nttr.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]                NTTR.CO.JP
g. [Organization]               NTT Resonant Incorporated
l. [Organization Type]          Corporation
m. [Administrative Contact]     MA20715JP
n. [Technical Contact]          MA20715JP
p. [Name Server]                ns1.goo.ne.jp
p. [Name Server]                ns2.goo.ne.jp
p. [Name Server]                ns.intervia.ad.jp
p. [Name Server]                ns.via.or.jp
s. [Signing Key]                
[State]                         Connected (2021/02/28)
[Registered Date]               2004/02/20
[Connected Date]                2004/02/24
[Last Update]                   2020/03/01 01:09:29 (JST)

Debug — Elasticsearch took 3622ms + 771ms