halaward.jp - robtex.com
halaward.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=1786394703 | ||||||
NS for
halaward.jp |
Same first word
Similar names
alrawdah.com |
darwalah.com |
alrawdah.ca |
alrawdha.com |
alwardah.net |
alrawdah.co |
alwardha.com |
drhawala.com |
hawaldar.com |
alrawdha.bh |
alrawdha.net |
dharwala.com |
alwardah.com |
DNS History
9 records (9 active, 0 former)
●NSdns01.muumuu-domain.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●NSdns02.muumuu-domain.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●NShalaward.jp2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●MXalt1.aspmx.l.google.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●MXalt2.aspmx.l.google.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●MXalt3.aspmx.l.google.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●MXalt4.aspmx.l.google.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●MXaspmx.l.google.com2019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
●A153.120.79.2162019-04-27 → 2026-08-10 · 2 obs
● 2026-08-10 22:12:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| halaward.jp | dns01.muumuu-domain.com, dns02.muumuu-domain.com | - |
✅ Authoritative Response
Server:160.251.249.62
NS records: dns01.muumuu-domain.com, dns02.muumuu-domain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for halaward.jp (unsigned zone)
⏱️ Timing
Total: 1425ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 153.120.79.216 |
| NS | 2 | dns02.muumuu-domain.com, dns01.muumuu-domain.com |
| MX | 5 | ALT1.ASPMX.L.GOOGLE.COM (pri: 5), ALT4.ASPMX.L.GOOGLE.COM (pri: 10)... |
| TXT | 1 | google-site-verification=zkZmpB2wgRWKmPA |
| SOA | 1 | halaward.jp postmaster.halaward.jp |
Analysis
Name Server Role
The NS records for halaward.jp point back to halaward.jp itself.
It is common to find dns02.muumuu-domain.com and dns01.muumuu-domain.com serving as name servers together with halaward.jp.
IP Addresses
halaward.jp resolves to just one IP address, 153.120.79.216.
Name Servers
The DNS delegation for halaward.jp uses three name servers — halaward.jp, dns01.muumuu-domain.com and dns02.muumuu-domain.com.
There is at least partial name server overlap between halaward.jp and other domains — bmishigaki.com, higashiyama-institute.com, gendagigo.jp and two more among them.
Each of the three hostnames points to exactly one IP address: halaward.jp points to 153.120.79.216, dns01.muumuu-domain.com points to 202.239.23.39 and dns02.muumuu-domain.com points to 160.251.249.62.
Mail Servers
Five mail servers handle halaward.jp: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between halaward.jp and other domains, including directfundings.com, swan.se, justin-yong.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.