oyabejc.com - robtex.com
oyabejc.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 162.43.117.67🇯🇵 XSERVER-AS162.43.112.0/21 XSERVER Inc. | ||||||
| PTR | sv13226.xserver.jp | ||||||
| NS | ns01.idcfcloud.com ⭐ | ||||||
| A | 210.140.183.89🇯🇵 IDC210.140.128.0/18 Frontier Inc. | ||||||
| NS | ns02.idcfcloud.com | ||||||
| A | 211.10.28.207🇯🇵 IDC211.10.0.0/19 Frontier Inc. | ||||||
| NS | ns03.idcfcloud.com | ||||||
| A | 202.230.203.7🇯🇵 IDC202.230.200.0/22 Frontier Inc. | ||||||
| MX | mail.exe.ne.jp ⭐ | ||||||
| A | 210.152.9.52🇯🇵 IDC210.152.0.0/20 Frontier Inc. | ||||||
| PTR | mail.exe.ne.jp | ||||||
| TXT | v=spf1 ip4:210.152.9.52 ip4:153.122.117.196 ip4:162.43.117.67 ~all | ||||||
| SOA | ns01.idcfcloud.comroot@oyabejc.com serial=15 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774609697 | ||||||
Previously NS for
oyabejc.com |
Same first word
oyabejc.com |
Similar names
DNS History
8 records (5 active, 3 former)
●NSns01.idcfcloud.com2017-12-13 → 2026-03-27 · 3 obs
● 2017-12-13 10:10:42
● 2026-03-27 11:18:46
●NSns02.idcfcloud.com2017-12-13 → 2026-03-27 · 3 obs
● 2017-12-13 10:10:42
● 2026-03-27 11:18:46
●NSns03.idcfcloud.com2017-12-13 → 2026-03-27 · 3 obs
● 2017-12-13 10:10:42
● 2026-03-27 11:18:46
○NSoyabejc.com2015-08-17 → 2016-11-28 · 4 obs
● 2016-11-28 01:20:22
○ 2017-12-13 10:10:42
○ 2026-03-27 11:18:46
○NSsv01.exe.ne.jp2015-08-17 → 2016-11-28 · 4 obs
● 2016-11-28 01:20:22
○ 2017-12-13 10:10:42
○ 2026-03-27 11:18:46
●MXmail.exe.ne.jp2017-12-13 → 2026-03-27 · 3 obs
● 2017-12-13 10:10:42
● 2026-03-27 11:18:46
○MXsv01.exe.ne.jp2015-08-17 → 2016-11-28 · 4 obs
● 2016-11-28 01:20:22
○ 2017-12-13 10:10:42
○ 2026-03-27 11:18:46
●A162.43.117.672026-02-26 → 2026-03-27 · 2 obs
● 2026-03-27 11:18:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| oyabejc.com | ns01.idcfcloud.com, ns02.idcfcloud.com, ns03.idcfcloud.com | 3 records |
✅ Authoritative Response
Server:210.140.183.89
NS records: ns01.idcfcloud.com, ns02.idcfcloud.com, ns03.idcfcloud.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for oyabejc.com (unsigned zone)
⏱️ Timing
Total: 411ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.43.117.67 |
| NS | 3 | ns01.idcfcloud.com, ns02.idcfcloud.com... |
| MX | 1 | mail.exe.ne.jp (pri: 10) |
| TXT | 1 | v=spf1 ip4:210.152.9.52 ip4:153.122.117. |
| SOA | 1 | ns01.idcfcloud.com root.oyabejc.com |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns01.idcfcloud.com, ns02.idcfcloud.com, ns03.idcfcloud.com)
Analysis
IP Addresses
oyabejc.com points to a single IP address: 162.43.117.67.
Other host names such as mail.zummy.net, d-fudousan.com, dns.kadogawa-shakyo.org, www.honmura-an.co.jp and fukumitsu-fudosan.com share IP numbers with oyabejc.com.
Name Servers
oyabejc.com is delegated to three name servers: ns01.idcfcloud.com, ns02.idcfcloud.com and ns03.idcfcloud.com.
At least part of the name servers for oyabejc.com are shared with other domains, for instance gslb.daily.co.jp, shigaquo.jp, ohugi.com, ainikoi.com and webshark.co.jp.
Host names with a single IP:
ns01.idcfcloud.com points to: 210.140.183.89
ns02.idcfcloud.com points to: 211.10.28.207
ns03.idcfcloud.com points to: 202.230.203.7
Mail Servers
The mail server for oyabejc.com is mail.exe.ne.jp.
oyabejc.com uses the same mail server setup as other domains, for instance curuntakaoka.com, makita-gr.com, d-fudousan.com, murotani.com and fukumitsu-fudosan.com.
Host mail.exe.ne.jp points to IP 210.152.9.52.