naruke.com - dns.ninja

naruke.com

DNSSEC⚠️ Not signed
A160.16.206.120🇯🇵 SAKURA-B160.16.128.0/17 (TOKYO) SAKURA Internet // EAST JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan
PTRssw40.secure-cms.net
NSns1.secure-cms.net
A180.131.139.43🇯🇵 AS131921180.131.136.0/22 GMO CLOUD K.K. GMO GlobalSign Holdings K.K.
PTRbq.ptr7.ptrcloud.net
NSns2.secure-cms.net
A153.121.55.89🇯🇵 SAKURA-B153.121.32.0/19 (TOKYO) SAKURA Internet // EAST JAPAN BACKBONE 1-8-14 Minami Honmachi, Chuo-ku, Osaka 541-0054, Japan
PTRwww4315up.sakura.ne.jp
NSns3.secure-cms.net
A49.212.154.50🇯🇵 SAKURA-C49.212.0.0/16 (7/OSAKA) SAKURA Internet // WEST JAPAN BACKBONE 1-8-15 Kyutaro-cho, Chuo Osaka 541-0056, Japan
PTRns3.secure-cms.net
MXsmtp.google.com
A2607:f8b0:4004:c08::1a🇺🇸 Google2607:f8b0:4004::/48
PTRbi-in-f26.1e100.net
A2607:f8b0:4004:c08::1b🇺🇸 Google2607:f8b0:4004::/48
PTRbi-in-f27.1e100.net
A2607:f8b0:4004:c09::1a🇺🇸 Google2607:f8b0:4004::/48
PTRbh-in-f26.1e100.net
A2607:f8b0:4004:c09::1b🇺🇸 Google2607:f8b0:4004::/48
PTRbh-in-f27.1e100.net
A142.250.31.27🇺🇸 Google142.250.31.0/24
A172.253.63.26🇺🇸 Google172.253.63.0/24
PTRbi-in-f26.1e100.net
A172.253.63.27🇺🇸 Google172.253.63.0/24
PTRbi-in-f27.1e100.net
A172.253.122.26🇺🇸 Google172.253.122.0/24
PTRbh-in-f26.1e100.net
A172.253.122.27🇺🇸 Google172.253.122.0/24
PTRbh-in-f27.1e100.net
TXTv=spf1 ip4:160.16.206.120 include:mx23.secure-cms.net a:www50149.sakura.ne.jp...
SOAns1.secure-cms.netpostmaster@secure-cms.net 2026-04-13 #1

com

Same first word

Similar names

DNS History

16 records (5 active, 11 former)

20162017201820192020202120222023202420252026NSns1.secure-cms.netns2.secure-cms.netns3.secure-cms.netns-210.dns.jp-e1.cloudn-service.comns-211.dns.jp-w1.cloudn-service.comns-212.dns.us-e1.cloudn-service.comns1.secure.netns2.secure.netMXsmtp.google.comin.sjc.mx.trendmicro.commwbgw1.ocn.ad.jpmwbgw2.ocn.ad.jpmx23.secure-cms.netA160.16.206.120153.254.73.17060.43.237.186
NSns-210.dns.jp-e1.cloudn-service.com2015-12-28 → 2018-07-29 · 5 obs
○ 2015-10-23 20:38:22
● 2015-12-28 15:04:24
● 2018-07-29 18:33:54
○ 2026-04-05 00:28:44
○ 2026-06-26 03:20:10
NSns-211.dns.jp-w1.cloudn-service.com2015-12-28 → 2018-07-29 · 5 obs
○ 2015-10-23 20:38:22
● 2015-12-28 15:04:24
● 2018-07-29 18:33:54
○ 2026-04-05 00:28:44
○ 2026-06-26 03:20:10
NSns-212.dns.us-e1.cloudn-service.com2015-12-28 → 2018-07-29 · 5 obs
○ 2015-10-23 20:38:22
● 2015-12-28 15:04:24
● 2018-07-29 18:33:54
○ 2026-04-05 00:28:44
○ 2026-06-26 03:20:10
NSns1.secure-cms.net2026-04-05 → 2026-06-26 · 3 obs
○ 2018-07-29 18:33:54
● 2026-04-05 00:28:44
● 2026-06-26 03:20:10
NSns1.secure.net2015-06-03 → 2015-10-23 · 4 obs
● 2015-06-03 16:10:04
● 2015-10-23 20:38:22
○ 2015-12-28 15:04:24
○ 2026-06-26 03:20:10
NSns2.secure-cms.net2026-04-05 → 2026-06-26 · 3 obs
○ 2018-07-29 18:33:54
● 2026-04-05 00:28:44
● 2026-06-26 03:20:10
NSns2.secure.net2015-06-03 → 2015-10-23 · 4 obs
● 2015-06-03 16:10:04
● 2015-10-23 20:38:22
○ 2015-12-28 15:04:24
○ 2026-06-26 03:20:10
NSns3.secure-cms.net2026-04-05 → 2026-06-26 · 3 obs
○ 2018-07-29 18:33:54
● 2026-04-05 00:28:44
● 2026-06-26 03:20:10
MXin.sjc.mx.trendmicro.com2015-06-03 → 2015-10-23 · 4 obs
● 2015-06-03 16:10:04
● 2015-10-23 20:38:22
○ 2015-12-28 15:04:24
○ 2026-06-26 03:20:10
MXmwbgw1.ocn.ad.jp2015-12-28 → 2018-07-29 · 5 obs
○ 2015-10-23 20:38:22
● 2015-12-28 15:04:24
● 2018-07-29 18:33:54
○ 2026-04-05 00:28:44
○ 2026-06-26 03:20:10
MXmwbgw2.ocn.ad.jp2015-12-28 → 2018-07-29 · 5 obs
○ 2015-10-23 20:38:22
● 2015-12-28 15:04:24
● 2018-07-29 18:33:54
○ 2026-04-05 00:28:44
○ 2026-06-26 03:20:10
MXmx23.secure-cms.net2026-04-05 → 2026-04-05 · 4 obs
○ 2018-07-29 18:33:54
● 2026-04-05 00:28:44
○ 2026-04-23 23:26:40
○ 2026-06-26 03:20:10
MXsmtp.google.com2026-04-23 → 2026-06-26 · 3 obs
○ 2026-04-05 00:28:44
● 2026-04-23 23:26:40
● 2026-06-26 03:20:10
A153.254.73.1702015-06-03 → 2015-10-23 · 4 obs
● 2015-06-03 16:10:04
● 2015-10-23 20:38:22
○ 2015-12-28 15:04:24
○ 2026-06-26 03:20:10
A160.16.206.1202026-04-05 → 2026-06-26 · 3 obs
○ 2018-07-29 18:33:54
● 2026-04-05 00:28:44
● 2026-06-26 03:20:10
A60.43.237.1862015-12-28 → 2018-07-29 · 5 obs
○ 2015-10-23 20:38:22
● 2015-12-28 15:04:24
● 2018-07-29 18:33:54
○ 2026-04-05 00:28:44
○ 2026-06-26 03:20:10

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net...-
naruke.comns1.secure-cms.net, ns2.secure-cms.net, ns3.secure-cms.net-

✅ Authoritative Response

Server:153.121.55.89

NS records: ns1.secure-cms.net, ns2.secure-cms.net, ns3.secure-cms.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for naruke.com (unsigned zone)

⏱️ Timing

Total: 935ms | Queries: -

📄 Records

TypeCountSample Data
A1160.16.206.120
NS3ns1.secure-cms.net, ns2.secure-cms.net...
MX1smtp.google.com (pri: 1)
TXT1v=spf1 ip4:160.16.206.120 include:mx23.s
SOA1ns1.secure-cms.net postmaster.secure-cms

Analysis

IP Addresses

naruke.com has exactly one IP address — 160.16.206.120.

ssw40.secure-cms.net, riken-spring.com, tk2-245-32116.vs.sakura.ne.jp plus two other host names have IP numbers in common with naruke.com.

Name Servers

naruke.com is served by three name servers: ns1.secure-cms.net, ns2.secure-cms.net and ns3.secure-cms.net.

naruke.com has at least partial name server overlap with other domains, such as esta-gas.co.jp, lightco.co.jp, katoubiken.jp and two others.

ns1.secure-cms.net has IP address 180.131.139.43, ns2.secure-cms.net has IP address 153.121.55.89 and ns3.secure-cms.net has IP address 49.212.154.50 — one address each.

Mail Servers

naruke.com uses one mail server — smtp.google.com.

The mail server setup of naruke.com matches that of other domains such as lemonaideco.org, flow-idea.com, innerpeacepsych.com and two others.

At least some of the mail servers used by naruke.com are shared with other domains: liv180.com, pushdigital.co.uk, rockay.com and two others among them.

smtp.google.com has 9 IP addresses: 142.250.31.27, 172.253.63.26, 172.253.63.27 plus 6 more.