started.jp - dns.ninja

started.jp

DNSSEC⚠️ Not signed
A59.106.186.115🇯🇵 SAKURA-B59.106.128.0/18 (7-128/TOKYO) SAKURA Internet // EAST JAPAN BACKBONE 1-8-14 Minami Honmachi, Chuo-ku, Osaka 541-0054, Japan
PTRusv0109.iqservs-jp.com
NSns-283.awsdns-35.com
A2600:9000:5301:1b00::1🇺🇸 Amazon2600:9000:5301::/48 - CloudFront
PTRns-283.awsdns-35.com
A205.251.193.27🇺🇸 Amazon205.251.193.0/24 prefix
PTRns-283.awsdns-35.com
NSns-1124.awsdns-12.org
A2600:9000:5304:6400::1🇺🇸 Amazon2600:9000:5304::/48 - CloudFront
PTRns-1124.awsdns-12.org
A205.251.196.100🇺🇸 Amazon205.251.196.0/24 prefix
PTRns-1124.awsdns-12.org
NSns-1649.awsdns-14.co.uk
A2600:9000:5306:7100::1🇺🇸 Amazon2600:9000:5306::/48 - CloudFront
PTRns-1649.awsdns-14.co.uk
A205.251.198.113🇺🇸 Amazon205.251.198.0/24 prefix
PTRns-1649.awsdns-14.co.uk
NSns-797.awsdns-35.net
A2600:9000:5303:1d00::1🇺🇸 Amazon2600:9000:5303::/48 - CloudFront
PTRns-797.awsdns-35.net
A205.251.195.29🇺🇸 Amazon205.251.195.0/24 prefix
PTRns-797.awsdns-35.net
TXTv=spf1 +a +mx redirect=spf.iq-servers.com
SOAns-283.awsdns-35.comawsdns-hostmaster@amazon.com serial=1

jp

DNSSEC🔒 Signed (DS record present)
NSz.dns.jp
NSa.dns.jp
NSb.dns.jp
NSc.dns.jp
NSd.dns.jp
NSe.dns.jp
NSf.dns.jp
NSg.dns.jp
NSh.dns.jp
SOAz.dns.jproot@dns.jp serial=1781076602

Same first word

Similar names

DNS History

21 records (5 active, 16 former)

20162017201820192020202120222023202420252026NSns-1124.awsdns-12.orgns-1649.awsdns-14.co.ukns-283.awsdns-35.comns-797.awsdns-35.netns-1508.awsdns-60.orgns-1894.awsdns-44.co.ukns-209.awsdns-26.comns-533.awsdns-02.netMXmx-proxy001.heteml.jpmx-proxy002.heteml.jpA59.106.186.11552.192.110.4952.193.1.12452.193.142.12652.193.50.12752.196.223.11052.68.80.14754.199.180.14654.238.184.2154.250.210.15254.92.67.185
NSns-1124.awsdns-12.org2026-02-21 → 2026-06-10 · 3 obs
○ 2017-07-22 20:58:08
● 2026-02-21 09:04:34
● 2026-06-10 08:35:52
NSns-1508.awsdns-60.org2015-08-17 → 2017-07-22 · 4 obs
● 2015-08-17 09:51:02
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
NSns-1649.awsdns-14.co.uk2026-02-21 → 2026-06-10 · 3 obs
○ 2017-07-22 20:58:08
● 2026-02-21 09:04:34
● 2026-06-10 08:35:52
NSns-1894.awsdns-44.co.uk2015-08-17 → 2017-07-22 · 4 obs
● 2015-08-17 09:51:02
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
NSns-209.awsdns-26.com2015-08-17 → 2017-07-22 · 4 obs
● 2015-08-17 09:51:02
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
NSns-283.awsdns-35.com2026-02-21 → 2026-06-10 · 3 obs
○ 2017-07-22 20:58:08
● 2026-02-21 09:04:34
● 2026-06-10 08:35:52
NSns-533.awsdns-02.net2015-08-17 → 2017-07-22 · 4 obs
● 2015-08-17 09:51:02
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
NSns-797.awsdns-35.net2026-02-21 → 2026-06-10 · 3 obs
○ 2017-07-22 20:58:08
● 2026-02-21 09:04:34
● 2026-06-10 08:35:52
MXmx-proxy001.heteml.jp2015-08-17 → 2017-07-22 · 4 obs
● 2015-08-17 09:51:02
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
MXmx-proxy002.heteml.jp2015-08-17 → 2017-07-22 · 4 obs
● 2015-08-17 09:51:02
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
A52.192.110.492015-12-04 → 2015-12-04 · 4 obs
○ 2015-08-17 09:51:02
● 2015-12-04 03:30:28
○ 2016-03-11 12:05:26
○ 2026-06-10 08:35:52
A52.193.1.1242016-03-11 → 2016-03-11 · 4 obs
○ 2015-12-04 03:30:28
● 2016-03-11 12:05:26
○ 2016-09-19 13:45:08
○ 2026-06-10 08:35:52
A52.193.142.1262017-07-22 → 2017-07-22 · 4 obs
○ 2016-09-19 13:45:08
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
A52.193.50.1272016-03-11 → 2016-03-11 · 4 obs
○ 2015-12-04 03:30:28
● 2016-03-11 12:05:26
○ 2016-09-19 13:45:08
○ 2026-06-10 08:35:52
A52.196.223.1102017-07-22 → 2017-07-22 · 4 obs
○ 2016-09-19 13:45:08
● 2017-07-22 20:58:08
○ 2026-02-21 09:04:34
○ 2026-06-10 08:35:52
A52.68.80.1472016-09-19 → 2016-09-19 · 4 obs
○ 2016-03-11 12:05:26
● 2016-09-19 13:45:08
○ 2017-07-22 20:58:08
○ 2026-06-10 08:35:52
A54.199.180.1462015-12-04 → 2015-12-04 · 4 obs
○ 2015-08-17 09:51:02
● 2015-12-04 03:30:28
○ 2016-03-11 12:05:26
○ 2026-06-10 08:35:52
A54.238.184.212015-08-17 → 2015-08-17 · 3 obs
● 2015-08-17 09:51:02
○ 2015-12-04 03:30:28
○ 2026-06-10 08:35:52
A54.250.210.1522016-09-19 → 2016-09-19 · 4 obs
○ 2016-03-11 12:05:26
● 2016-09-19 13:45:08
○ 2017-07-22 20:58:08
○ 2026-06-10 08:35:52
A54.92.67.1852015-08-17 → 2015-08-17 · 3 obs
● 2015-08-17 09:51:02
○ 2015-12-04 03:30:28
○ 2026-06-10 08:35:52
A59.106.186.1152026-02-21 → 2026-06-10 · 3 obs
○ 2017-07-22 20:58:08
● 2026-02-21 09:04:34
● 2026-06-10 08:35:52

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
jpa.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp...-
started.jpns-797.awsdns-35.net, ns-1649.awsdns-14.co.uk, ns-283.awsdns-35.com, ns-1124.awsdns-12.org-

✅ Authoritative Response

Server:205.251.195.29

NS records: ns-797.awsdns-35.net, ns-1649.awsdns-14.co.uk, ns-283.awsdns-35.com, ns-1124.awsdns-12.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for started.jp (unsigned zone)

⏱️ Timing

Total: 1053ms | Queries: -

📄 Records

TypeCountSample Data
A159.106.186.115
NS4ns-1124.awsdns-12.org, ns-1649.awsdns-14.co.uk...
TXT1v=spf1 +a +mx redirect=spf.iq-servers.co
SOA1ns-283.awsdns-35.com awsdns-hostmaster.a

Analysis

IP Addresses

started.jp points to one IP number: 59.106.186.115.

Additional host names — including jbr819.com and usv0109.iqservs-jp.com — share IP numbers with started.jp.

Name Servers

started.jp is delegated to 4 name servers, ns-283.awsdns-35.com, ns-797.awsdns-35.net, ns-1124.awsdns-12.org and ns-1649.awsdns-14.co.uk.

started.jp at least partially shares name servers with other domains, for instance slicingmachines.com, landalv.com, flcloud.com.br and two other.

ns-283.awsdns-35.com, ns-797.awsdns-35.net, ns-1124.awsdns-12.org and ns-1649.awsdns-14.co.uk all point to exactly two IP numbers each: ns-283.awsdns-35.com205.251.193.27 and 2600:9000:5301:1b00::1; ns-797.awsdns-35.net205.251.195.29 and 2600:9000:5303:1d00::1; ns-1124.awsdns-12.org205.251.196.100 and 2600:9000:5304:6400::1; ns-1649.awsdns-14.co.uk205.251.198.113 and 2600:9000:5306:7100::1.