haloreach.jp - robtex.com
haloreach.jp
| DNSSEC | ⚠️ Not signed | ||||||
| A | 20.70.246.20🇦🇺 Microsoft20.64.0.0/10 | ||||||
| A | 20.76.201.171🇳🇱 Microsoft20.64.0.0/10 | ||||||
| A | 20.112.250.133🇺🇸 Microsoft20.64.0.0/10 | ||||||
| A | 20.231.239.246🇺🇸 Microsoft20.192.0.0/10 | ||||||
| A | 20.236.44.162🇺🇸 Microsoft20.192.0.0/10 | ||||||
| NS | ns1-02.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::2🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| A | 13.107.236.2🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| NS | ns2-02.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| A | 150.171.21.2🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| NS | ns3-02.azure-dns.org | ||||||
| A | 2a01:111:4000:700::2🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| A | 204.14.183.2🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| NS | ns4-02.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| A | 208.84.5.2🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| SOA | ns1-02.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
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=1774361702 | ||||||
Same first word
Similar names
DNS History
19 records (9 active, 10 former)
●NSns1-02.azure-dns.com2026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
○NSns1.msft.net2015-08-03 → 2018-05-18 · 4 obs
● 2018-05-18 10:12:34
○ 2026-02-28 12:17:30
○ 2026-03-24 14:26:54
●NSns2-02.azure-dns.net2026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
○NSns2.msft.net2015-08-03 → 2018-05-18 · 4 obs
● 2018-05-18 10:12:34
○ 2026-02-28 12:17:30
○ 2026-03-24 14:26:54
●NSns3-02.azure-dns.org2026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
○NSns3.msft.net2015-08-03 → 2018-05-18 · 4 obs
● 2018-05-18 10:12:34
○ 2026-02-28 12:17:30
○ 2026-03-24 14:26:54
●NSns4-02.azure-dns.info2026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
○NSns4.msft.net2015-08-03 → 2018-05-18 · 4 obs
● 2018-05-18 10:12:34
○ 2026-02-28 12:17:30
○ 2026-03-24 14:26:54
○A104.215.95.1872018-05-18 → 2018-05-18 · 4 obs
● 2018-05-18 10:12:34
○ 2026-02-28 12:17:30
○ 2026-03-24 14:26:54
●A20.112.250.1332026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
●A20.231.239.2462026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
●A20.236.44.1622026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
●A20.70.246.202026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
●A20.76.201.1712026-02-28 → 2026-03-24 · 3 obs
● 2026-02-28 12:17:30
● 2026-03-24 14:26:54
○A40.84.199.2332017-01-08 → 2017-01-08 · 4 obs
● 2017-01-08 16:24:50
○ 2018-05-18 10:12:34
○ 2026-03-24 14:26:54
○A52.164.206.562018-05-18 → 2018-05-18 · 4 obs
● 2018-05-18 10:12:34
○ 2026-02-28 12:17:30
○ 2026-03-24 14:26:54
○A52.178.167.1092017-01-08 → 2017-01-08 · 4 obs
● 2017-01-08 16:24:50
○ 2018-05-18 10:12:34
○ 2026-03-24 14:26:54
○A64.4.6.1002015-08-03 → 2016-04-08 · 4 obs
● 2016-04-08 14:15:54
○ 2017-01-08 16:24:50
○ 2026-03-24 14:26:54
○A65.55.39.102015-08-03 → 2016-04-08 · 4 obs
● 2016-04-08 14:15:54
○ 2017-01-08 16:24:50
○ 2026-03-24 14:26:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| haloreach.jp | ns2-02.azure-dns.net, ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns3-02.azure-dns.org | - |
✅ Authoritative Response
Server:204.14.183.2
NS records: ns2-02.azure-dns.net, ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns3-02.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for haloreach.jp (unsigned zone)
⏱️ Timing
Total: 652ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 5 | 20.76.201.171, 20.112.250.133... |
| NS | 4 | ns1-02.azure-dns.com, ns2-02.azure-dns.net... |
| SOA | 1 | ns1-02.azure-dns.com azuredns-hostmaster |
Analysis
IP Addresses
Five IP numbers are pointed to by haloreach.jp: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.
other host names including browsewithconfidence.ca, microsofthyper-v.com.ve, betamsn.com, adcentercommunityblog.com and microsoftrepair.com share IP numbers with haloreach.jp.
Name Servers
haloreach.jp is delegated to four name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.
haloreach.jp at least partially shares name servers with other domains, for instance itbubble.ru, medber.com, us-cloudflare-prod.azure.lnrsg.io, croslite.net and moottoriradat.fi.
Host names with two IP numbers:
ns1-02.azure-dns.com points to 2603:1061:0:700::2 and 13.107.236.2; ns4-02.azure-dns.info points to 2620:1ec:bda:700::2 and 208.84.5.2; ns2-02.azure-dns.net points to 2620:1ec:8ec:700::2 and 150.171.21.2; ns3-02.azure-dns.org points to 2a01:111:4000:700::2 and 204.14.183.2.