fleetcommand.jp - dns.ninja
fleetcommand.jp
| DNSSEC | ⚠️ Not signed | ||||||
| A | 35.196.206.7🇺🇸 Google35.196.192.0/20 | ||||||
| PTR | 7.206.196.35.bc.googleusercontent.com | ||||||
| NS | ns-828.awsdns-39.net ⭐ | ||||||
| A | 2600:9000:5303:3c00::1🇺🇸 Amazon2600:9000:5303::/48 - CloudFront | ||||||
| PTR | ns-828.awsdns-39.net | ||||||
| A | 205.251.195.60🇺🇸 Amazon205.251.195.0/24 prefix | ||||||
| PTR | ns-828.awsdns-39.net | ||||||
| NS | ns-1440.awsdns-52.org | ||||||
| A | 2600:9000:5305:a000::1🇺🇸 Amazon2600:9000:5305::/48 - CloudFront | ||||||
| PTR | ns-1440.awsdns-52.org | ||||||
| A | 205.251.197.160🇺🇸 Amazon205.251.197.0/24 prefix | ||||||
| PTR | ns-1440.awsdns-52.org | ||||||
| NS | ns-171.awsdns-21.com | ||||||
| A | 2600:9000:5300:ab00::1🇺🇸 Amazon2600:9000:5300::/48 - CloudFront | ||||||
| PTR | ns-171.awsdns-21.com | ||||||
| A | 205.251.192.171🇺🇸 Amazon205.251.192.0/24 prefix | ||||||
| PTR | ns-171.awsdns-21.com | ||||||
| NS | ns-1886.awsdns-43.co.uk | ||||||
| A | 2600:9000:5307:5e00::1🇺🇸 Amazon2600:9000:5307::/48 - CloudFront | ||||||
| PTR | ns-1886.awsdns-43.co.uk | ||||||
| A | 205.251.199.94🇺🇸 Amazon205.251.199.0/24 prefix | ||||||
| PTR | ns-1886.awsdns-43.co.uk | ||||||
| SOA | ns-828.awsdns-39.netawsdns-hostmaster@amazon.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=1785566702 | ||||||
Same first word
fleetcommand.jp |
fleetcommand.io |
fleetcommand.com |
DNS History
5 records (5 active, 0 former)
●NSns-1440.awsdns-52.org2026-02-16 → 2026-08-01 · 2 obs
● 2026-08-01 07:47:58
●NSns-171.awsdns-21.com2026-02-16 → 2026-08-01 · 2 obs
● 2026-08-01 07:47:58
●NSns-1886.awsdns-43.co.uk2026-02-16 → 2026-08-01 · 2 obs
● 2026-08-01 07:47:58
●NSns-828.awsdns-39.net2026-02-16 → 2026-08-01 · 2 obs
● 2026-08-01 07:47:58
●A35.196.206.72026-02-16 → 2026-08-01 · 2 obs
● 2026-08-01 07:47:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| fleetcommand.jp | ns-171.awsdns-21.com, ns-828.awsdns-39.net, ns-1440.awsdns-52.org, ns-1886.awsdns-43.co.uk | - |
✅ Authoritative Response
Server:205.251.192.171
NS records: ns-171.awsdns-21.com, ns-828.awsdns-39.net, ns-1440.awsdns-52.org, ns-1886.awsdns-43.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fleetcommand.jp (unsigned zone)
⏱️ Timing
Total: 740ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.196.206.7 |
| NS | 4 | ns-1440.awsdns-52.org, ns-171.awsdns-21.com... |
| SOA | 1 | ns-828.awsdns-39.net awsdns-hostmaster.a |
Analysis
IP Addresses
fleetcommand.jp directs to one IP number, which is 35.196.206.7.
Host names such as scohosting.wpengine.com, pierplay.com and 7.206.196.35.bc.googleusercontent.com share their IP numbers with fleetcommand.jp.
Name Servers
The domain fleetcommand.jp is delegated to these four name servers: ns-171.awsdns-21.com, ns-828.awsdns-39.net, ns-1440.awsdns-52.org and ns-1886.awsdns-43.co.uk.
The name servers of fleetcommand.jp overlap at least partially with those of other domains — among them ipscomputers.com, compreunmillon.com, paulsylling.com and two more.
Each of the four hosts ns-171.awsdns-21.com, ns-828.awsdns-39.net, ns-1440.awsdns-52.org and ns-1886.awsdns-43.co.uk has two IP addresses. ns-171.awsdns-21.com points to 205.251.192.171 and 2600:9000:5300:ab00::1. ns-828.awsdns-39.net points to 205.251.195.60 and 2600:9000:5303:3c00::1. ns-1440.awsdns-52.org points to 205.251.197.160 and 2600:9000:5305:a000::1. ns-1886.awsdns-43.co.uk points to 205.251.199.94 and 2600:9000:5307:5e00::1.