inmarks.jp - robtex.com
inmarks.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=1784041205 | ||||||
Previously MX for
inmarks.jp |
Same first word
Similar names
DNS History
10 records (6 active, 4 former)
●NSdns01.muumuu-domain.com2026-06-25 → 2026-07-14 · 3 obs
● 2026-06-25 14:54:46
● 2026-07-14 15:39:32
●NSdns02.muumuu-domain.com2026-06-25 → 2026-07-14 · 3 obs
● 2026-06-25 14:54:46
● 2026-07-14 15:39:32
○NSns3.sphere.ad.jp2015-05-24 → 2017-04-09 · 4 obs
● 2017-04-09 03:19:48
○ 2026-06-25 14:54:46
○ 2026-07-14 15:39:32
○NSns4.sphere.ad.jp2015-05-24 → 2017-04-09 · 4 obs
● 2017-04-09 03:19:48
○ 2026-06-25 14:54:46
○ 2026-07-14 15:39:32
●MXcluster1.us.messagelabs.com2026-06-25 → 2026-07-14 · 3 obs
● 2026-06-25 14:54:46
● 2026-07-14 15:39:32
●MXcluster1a.us.messagelabs.com2026-06-25 → 2026-07-14 · 3 obs
● 2026-06-25 14:54:46
● 2026-07-14 15:39:32
○MXinmarks.jp2015-05-24 → 2017-04-09 · 4 obs
● 2017-04-09 03:19:48
○ 2026-06-25 14:54:46
○ 2026-07-14 15:39:32
●MXv2101-151.mailsecure.jp2026-06-25 → 2026-07-14 · 3 obs
● 2026-06-25 14:54:46
● 2026-07-14 15:39:32
○A119.245.150.872015-05-24 → 2017-04-09 · 4 obs
● 2017-04-09 03:19:48
○ 2026-06-25 14:54:46
○ 2026-07-14 15:39:32
●A160.251.52.1822026-06-25 → 2026-07-14 · 3 obs
● 2026-06-25 14:54:46
● 2026-07-14 15:39:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | f.dns.jp, e.dns.jp, a.dns.jp, h.dns.jp... | - |
| inmarks.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 inmarks.jp (unsigned zone)
⏱️ Timing
Total: 1364ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.251.52.182 |
| NS | 2 | dns02.muumuu-domain.com, dns01.muumuu-domain.com |
| MX | 3 | cluster1a.us.messagelabs.com (pri: 20), cluster1.us.messagelabs.com (pri: 10)... |
| TXT | 4 | google-site-verification=Ql9qdAFEEJIQHZA, v=spf1 +ip4:164.70.83.151/32 +ip4:118.27... |
| SOA | 1 | dns01.muumuu-domain.com postmaster.inmar |
Analysis
IP Addresses
inmarks.jp has exactly one IP address — 160.251.52.182.
anime-chi.jp, vagrant.jp, v160-251-52-182.c3do.static.cnode.io plus two other host names have IP numbers in common with inmarks.jp.
Name Servers
The NS records for inmarks.jp delegate to dns01.muumuu-domain.com and dns02.muumuu-domain.com.
The name server configuration of inmarks.jp is shared with other domains, for instance yamani-net.com, wateraid.jp, connect-hearts.org and two others.
There is at least partial name server overlap between inmarks.jp and other domains — buzz8eight.com, svdragons.com, hahyuu.net and two more among them.
dns01.muumuu-domain.com → 202.239.23.39 and dns02.muumuu-domain.com → 160.251.249.62: one IP number per host name.
Mail Servers
Incoming mail for inmarks.jp is delivered via three mail servers: v2101-151.mailsecure.jp, cluster1.us.messagelabs.com and cluster1a.us.messagelabs.com.
At least some of the mail servers used by inmarks.jp are shared with other domains: ikemicro.com, toll.co.nz, centexinsurance.com and two others among them.
These mail servers are routinely seen in conjunction with the mail servers mailneo.neowiz.com and mailwiz.neowiz.com.
Hosts with 8 IP addresses each:
cluster1.us.messagelabs.com maps to 67.219.246.208, 67.219.246.210, 67.219.247.106 and 5 additional IP addresses.
Host names resolving to a single IP address:
v2101-151.mailsecure.jp resolves to the IP address 164.70.83.151.
cluster1a.us.messagelabs.com resolves to the IP address 34.75.172.113.