sdnet.ne.jp - robtex.com

sdnet.ne.jp

DNSSECโš ๏ธ Not signed
A150.60.157.165๐Ÿ‡ฏ๐Ÿ‡ต CPI-NET150.60.0.0/16 KDDI Web Communications Inc.
NSns6.cpi.ad.jp โญ
A122.200.253.233๐Ÿ‡ฏ๐Ÿ‡ต CPI-NET122.200.224.0/19
PTRns6.cpi.ad.jp
NSns7.cpi.ad.jp
A122.200.212.133๐Ÿ‡ฏ๐Ÿ‡ต CPI-NET122.200.192.0/19
PTRns7.cpi.ad.jp
MXvlmx-air.secure.ne.jp โญ
A111.96.116.216๐Ÿ‡ฏ๐Ÿ‡ต KDDI111.96.0.0/16
A111.96.117.216๐Ÿ‡ฏ๐Ÿ‡ต KDDI111.96.0.0/16
TXTv=spf1 include:spf.secure.ne.jp -all
SOAns6.cpi.ad.jphostmaster@cpi.ad.jp 2024-10-22 #1

ne.jp

DNSSECโš ๏ธ Not signed
TXTne.jp.
WOT: SAFE (87/100)

.ne.jp - Japanese Network Service Domain

.ne.jp is a second-level domain under Japan's country-code top-level domain (.jp), designated specifically for network service providers. It is managed by Japan Registry Services Co., Ltd. (JPRS), the official registry for all .jp domains since 2002.

Purpose and Usage

The .ne.jp domain is reserved for organizations providing network-related services in Japan, including:

  • Internet Service Providers (ISPs)
  • Telecommunications companies
  • Network infrastructure providers
  • Online service platforms

This domain type has a "Reserved" status, meaning registrations are restricted to qualifying network service entities rather than being openly available to the general public.

DNS Infrastructure

The domain operates on Japan's authoritative DNS infrastructure:

Record TypeDetails
Nameserversa.dns.jp through h.dns.jp (8 servers)
Primary SOAz.dns.jp
DNSSECSigned with validated chain of trust from root
Authoritative IP203.119.40.1

History

The .jp ccTLD was delegated on August 5, 1986, making it one of the earliest country-code domains. The ne.jp second-level domain was established as part of Japan's structured domain hierarchy to organize registrations by purpose (similar to co.jp for companies, or.jp for organizations, and ac.jp for academic institutions).

Previously NS for

Previously MX for

Subdomains

Same first word

Similar names

DNS History

12 records (4 active, 8 former)

20162017201820192020202120222023202420252026NSns6.cpi.ad.jpns7.cpi.ad.jpns-tk011.ocn.ad.jpns01.sdnet.jpsdnet.ne.jpMXvlmx-air.secure.ne.jpsdnet.ne.jpvlmx20.secure.ne.jpvlmx21.secure.ne.jpvlmx22.secure.ne.jpA150.60.157.165219.163.51.54
โ—‹NSns-tk011.ocn.ad.jp2015-07-25 โ†’ 2016-09-05 ยท 4 obs
โ— 2015-07-25 00:31:30
โ— 2016-09-05 18:27:36
โ—‹ 2017-06-30 23:51:30
โ—‹ 2026-05-15 00:23:42
โ—‹NSns01.sdnet.jp2015-07-25 โ†’ 2016-09-05 ยท 4 obs
โ— 2015-07-25 00:31:30
โ— 2016-09-05 18:27:36
โ—‹ 2017-06-30 23:51:30
โ—‹ 2026-05-15 00:23:42
โ—NSns6.cpi.ad.jp2017-06-30 โ†’ 2026-05-15 ยท 3 obs
โ—‹ 2016-09-05 18:27:36
โ— 2017-06-30 23:51:30
โ— 2026-05-15 00:23:42
โ—NSns7.cpi.ad.jp2017-06-30 โ†’ 2026-05-15 ยท 3 obs
โ—‹ 2016-09-05 18:27:36
โ— 2017-06-30 23:51:30
โ— 2026-05-15 00:23:42
โ—‹NSsdnet.ne.jp2015-07-25 โ†’ 2016-09-05 ยท 4 obs
โ— 2015-07-25 00:31:30
โ— 2016-09-05 18:27:36
โ—‹ 2017-06-30 23:51:30
โ—‹ 2026-05-15 00:23:42
โ—‹MXsdnet.ne.jp2015-07-25 โ†’ 2016-09-05 ยท 4 obs
โ— 2015-07-25 00:31:30
โ— 2016-09-05 18:27:36
โ—‹ 2017-06-30 23:51:30
โ—‹ 2026-05-15 00:23:42
โ—MXvlmx-air.secure.ne.jp2026-04-10 โ†’ 2026-05-15 ยท 3 obs
โ—‹ 2017-06-30 23:51:30
โ— 2026-04-10 12:51:28
โ— 2026-05-15 00:23:42
โ—‹MXvlmx20.secure.ne.jp2017-06-30 โ†’ 2017-06-30 ยท 4 obs
โ—‹ 2016-09-05 18:27:36
โ— 2017-06-30 23:51:30
โ—‹ 2026-04-10 12:51:28
โ—‹ 2026-05-15 00:23:42
โ—‹MXvlmx21.secure.ne.jp2017-06-30 โ†’ 2017-06-30 ยท 4 obs
โ—‹ 2016-09-05 18:27:36
โ— 2017-06-30 23:51:30
โ—‹ 2026-04-10 12:51:28
โ—‹ 2026-05-15 00:23:42
โ—‹MXvlmx22.secure.ne.jp2017-06-30 โ†’ 2017-06-30 ยท 4 obs
โ—‹ 2016-09-05 18:27:36
โ— 2017-06-30 23:51:30
โ—‹ 2026-04-10 12:51:28
โ—‹ 2026-05-15 00:23:42
โ—A150.60.157.1652017-06-30 โ†’ 2026-05-15 ยท 3 obs
โ—‹ 2016-09-05 18:27:36
โ— 2017-06-30 23:51:30
โ— 2026-05-15 00:23:42
โ—‹A219.163.51.542015-07-25 โ†’ 2016-09-05 ยท 4 obs
โ— 2015-07-25 00:31:30
โ— 2016-09-05 18:27:36
โ—‹ 2017-06-30 23:51:30
โ—‹ 2026-05-15 00:23:42

๐Ÿ” DNS Trace

๐Ÿ“‹ Delegation Chain

ZoneNameserversGlue
jph.dns.jp, c.dns.jp, f.dns.jp, e.dns.jp...-
sdnet.ne.jpns6.cpi.ad.jp, ns7.cpi.ad.jp2 records

โœ… Authoritative Response

Server:122.200.253.233

NS records: ns6.cpi.ad.jp, ns7.cpi.ad.jp

๐Ÿ”’ DNSSEC Status

โš ๏ธ Insecure (no DNSSEC)

No DS record for sdnet.ne.jp (unsigned zone)

โฑ๏ธ Timing

Total: 813ms | Queries: -

๐Ÿ“„ Records

TypeCountSample Data
A1150.60.157.165
NS2ns7.cpi.ad.jp, ns6.cpi.ad.jp
MX1vlmx-air.secure.ne.jp (pri: 10)
TXT1v=spf1 include:spf.secure.ne.jp -all
SOA1ns6.cpi.ad.jp hostmaster.cpi.ad.jp

๐Ÿ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns7.cpi.ad.jp, ns6.cpi.ad.jp)

Analysis

Hierarchy

The parent of www.sdnet.ne.jp is sdnet.ne.jp.

IP Addresses

sdnet.ne.jp points to a single IP address: 150.60.157.165.

Other host names such as www.torinobyoin.com, yamada-kajuen.com, waproo-kenchiku.com, adachikumihimokan.com and www.sdnet.ne.jp share IPs with sdnet.ne.jp.

Name Servers

Two name servers ns6.cpi.ad.jp and ns7.cpi.ad.jp handle the delegation for sdnet.ne.jp.

sdnet.ne.jp shares the same name server setup as other domains, for example tonpiro.com, smilenet.tech, mikado.in, ezo.co.jp and int-acc.or.jp.

sdnet.ne.jp at least partially shares name servers with other domains, for example 48.146.115.in-addr.arpa, 210.199.158.in-addr.arpa, 161.60.150.in-addr.arpa, 171.199.158.in-addr.arpa and 237.164.202.in-addr.arpa.

Name servers ns0.cpi.ad.jp, ns1.cpi.ad.jp, ns2.cpi.ad.jp, ns3.cpi.ad.jp, ns4.cpi.ad.jp, ns5.cpi.ad.jp and cpi.ad.jp are commonly used together.

Host names with one IP number:

ns6.cpi.ad.jp points to 122.200.253.233; ns7.cpi.ad.jp points to 122.200.212.133.

Mail Servers

The vlmx-air.secure.ne.jp mail server handles sdnet.ne.jp.

sdnet.ne.jp shares the same mail server setup as other domains, including nidec-machinery.com, tochigi-agri.or.jp, kpn.co.jp, w3lab.com and riversidehotel.info.

vlmx-air.secure.ne.jp points to two IP numbers: 111.96.116.216 and 111.96.117.216.