halcom.jp - robtex.com
halcom.jp
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1786862702 | ||||||
Same first word
halcom.co.uk |
halcom.rs |
halcom.vn |
halcom.ba |
halcom.org |
halcom.cn |
halcom.de |
halcom.jp |
halcom.no |
halcom.eu |
halcom.com |
halcom.net |
halcom.it |
halcom.fr |
halcom.info |
halcom.nl |
halcom.co.jp |
halcom.biz |
halcom.si |
Similar names
DNS History
16 records (13 active, 3 former)
●NS01.dnsv.jp2026-04-23 → 2026-08-16 · 3 obs
● 2026-04-23 23:25:14
● 2026-08-16 06:56:24
●NS02.dnsv.jp2026-04-23 → 2026-08-16 · 3 obs
● 2026-04-23 23:25:14
● 2026-08-16 06:56:24
●NS03.dnsv.jp2026-04-23 → 2026-08-16 · 3 obs
● 2026-04-23 23:25:14
● 2026-08-16 06:56:24
●NS04.dnsv.jp2026-04-23 → 2026-08-16 · 3 obs
● 2026-04-23 23:25:14
● 2026-08-16 06:56:24
○NSdns2.ixent.ne.jp2015-06-09 → 2016-09-22 · 4 obs
● 2016-09-22 16:27:44
○ 2026-04-23 23:25:14
○ 2026-08-16 06:56:24
○NSns2.halcom.co.jp2015-06-09 → 2016-09-22 · 4 obs
● 2016-09-22 16:27:44
○ 2026-04-23 23:25:14
○ 2026-08-16 06:56:24
●MXalt1.aspmx.l.google.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
●MXalt2.aspmx.l.google.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
●MXalt3.aspmx.l.google.com2026-04-23 → 2026-08-16 · 3 obs
● 2026-04-23 23:25:14
● 2026-08-16 06:56:24
●MXalt4.aspmx.l.google.com2026-04-23 → 2026-08-16 · 3 obs
● 2026-04-23 23:25:14
● 2026-08-16 06:56:24
●MXaspmx.l.google.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
●MXaspmx2.googlemail.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
●MXaspmx3.googlemail.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
●MXaspmx4.googlemail.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
●MXaspmx5.googlemail.com2015-06-09 → 2026-08-16 · 2 obs
● 2026-08-16 06:56:24
○A210.143.103.242015-06-09 → 2016-09-22 · 4 obs
● 2016-09-22 16:27:44
○ 2026-04-23 23:25:14
○ 2026-08-16 06:56:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | d.dns.jp, e.dns.jp, f.dns.jp, c.dns.jp... | - |
| halcom.jp | 04.dnsv.jp, 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp | 7 records |
✅ Authoritative Response
Server:157.7.35.53
NS records: 04.dnsv.jp, 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for halcom.jp (unsigned zone)
⏱️ Timing
Total: 614ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | 01.dnsv.jp, 02.dnsv.jp... |
| MX | 9 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | 01.dnsv.jp hostmaster.dnsv.jp |
📌 Glue Records Collected
Total: 7
Out-of-bailiwick: 7 (01.dnsv.jp, 01.dnsv.jp, 02.dnsv.jp...)
Analysis
Name Servers
The NS records for halcom.jp point to four name servers: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp and 04.dnsv.jp.
halcom.jp shares at least some of its name servers with other domains, including ieshige.com, hirotsu.clinic, girls-health.jp and two others.
Host names that have two IP addresses:
01.dnsv.jp directs traffic to 157.7.32.53 and 2400:8500:3300::53.
03.dnsv.jp directs traffic to 157.7.34.53 and 2400:8500:3000::53.
04.dnsv.jp directs traffic to 157.7.35.53 and 2400:8500:3fff::53.
Host names that point to one IP address:
02.dnsv.jp has the IP address 157.7.33.53.
Mail Servers
halcom.jp is handled by 9 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 6 other.
There is at least a partial MX overlap between halcom.jp and other domains, including armorysystem.com, jennydayco.com, itransfers.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx4.googlemail.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
aspmx5.googlemail.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.
aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.
Both aspmx4.googlemail.com and alt3.aspmx.l.google.com resolve to 192.178.223.27 IP addresses each.
Both aspmx5.googlemail.com and alt4.aspmx.l.google.com resolve to 2a00:1450:400c:c23::1a IP addresses each.
Both aspmx5.googlemail.com and alt4.aspmx.l.google.com resolve to 172.253.157.27 IP addresses each.