m3connect.jp - robtex.com
m3connect.jp
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-1217.awsdns-24.org ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5304:c100::1🇺🇸 Amazon2600:9000:5304::/48 - CloudFront | ||||||
| PTR | ns-1217.awsdns-24.org | ||||||
| A | 205.251.196.193🇺🇸 Amazon205.251.196.0/24 prefix | ||||||
| PTR | ns-1217.awsdns-24.org | ||||||
| NS | ns-158.awsdns-19.com ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5300:9e00::1🇺🇸 Amazon2600:9000:5300::/48 - CloudFront | ||||||
| PTR | ns-158.awsdns-19.com | ||||||
| A | 205.251.192.158🇺🇸 Amazon205.251.192.0/24 prefix | ||||||
| PTR | ns-158.awsdns-19.com | ||||||
| NS | ns-1709.awsdns-21.co.uk ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5306:ad00::1🇺🇸 Amazon2600:9000:5306::/48 - CloudFront | ||||||
| PTR | ns-1709.awsdns-21.co.uk | ||||||
| A | 205.251.198.173🇺🇸 Amazon205.251.198.0/24 prefix | ||||||
| PTR | ns-1709.awsdns-21.co.uk | ||||||
| NS | ns-921.awsdns-51.net ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5303:9900::1🇺🇸 Amazon2600:9000:5303::/48 - CloudFront | ||||||
| PTR | ns-921.awsdns-51.net | ||||||
| A | 205.251.195.153🇺🇸 Amazon205.251.195.0/24 prefix | ||||||
| PTR | ns-921.awsdns-51.net | ||||||
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=1774850403 | ||||||
Same first word
m3connect.eu |
m3connect.at |
m3connect.de |
m3connect.jp |
m3connect.com |
m3connect.cloud |
m3connect.org |
m3connect.mobi |
DNS History
6 records (4 active, 2 former)
●NSns-1217.awsdns-24.org2018-05-09 → 2026-03-30 · 2 obs
● 2026-03-30 06:27:58
●NSns-158.awsdns-19.com2018-05-09 → 2026-03-30 · 2 obs
● 2026-03-30 06:27:58
●NSns-1709.awsdns-21.co.uk2018-05-09 → 2026-03-30 · 2 obs
● 2026-03-30 06:27:58
●NSns-921.awsdns-51.net2018-05-09 → 2026-03-30 · 2 obs
● 2026-03-30 06:27:58
○A13.114.163.1802018-05-09 → 2018-05-09 · 3 obs
○ 2026-02-25 02:38:06
○ 2026-03-30 06:27:58
○A54.92.105.202018-05-09 → 2018-05-09 · 3 obs
○ 2026-02-25 02:38:06
○ 2026-03-30 06:27:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| m3connect.jp | ns-921.awsdns-51.net, ns-1217.awsdns-24.org, ns-1709.awsdns-21.co.uk, ns-158.awsdns-19.com | - |
✅ Authoritative Response
Server:205.251.198.173
NS records: ns-921.awsdns-51.net, ns-1217.awsdns-24.org, ns-1709.awsdns-21.co.uk, ns-158.awsdns-19.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for m3connect.jp (unsigned zone)
⏱️ Timing
Total: 677ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
m3connect.jp delegates to four name servers: ns-158.awsdns-19.com, ns-921.awsdns-51.net, ns-1217.awsdns-24.org and ns-1709.awsdns-21.co.uk.
m3connect.jp at least partially shares name servers with other domains, including iranvi.ca, links.com.au, yorkweekly.com, cardioflux.com and nexcomtelecom.com.
These name servers are often used with ns-661.awsdns-18.net and ns-1991.awsdns-56.co.uk.
Host names with two IP numbers: ns-158.awsdns-19.com points to 2600:9000:5300:9e00::1 and 205.251.192.158; ns-921.awsdns-51.net points to 2600:9000:5303:9900::1 and 205.251.195.153; ns-1217.awsdns-24.org points to 2600:9000:5304:c100::1 and 205.251.196.193; ns-1709.awsdns-21.co.uk points to 2600:9000:5306:ad00::1 and 205.251.198.173.