ptcms.dev - dns.ninja
ptcms.dev
dev
| DNSSEC | π Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com β | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
ptaki.dev |
ptaku.dev |
ptal.dev |
ptallen.dev |
ptamrakar.dev |
ptap.dev |
ptaszek.dev |
ptatk.dev |
ptatoolkit.dev |
ptaylor.dev |
ptb.dev |
ptbarnum.dev |
ptbox.dev |
ptc-runner.dev |
ptc.dev |
ptcgl.dev |
ptchen.dev |
ptchr.dev |
ptci.dev |
ptcin.dev |
Next names
DNS History
5 records (5 active, 0 former)
βNSns1bcp.name.com2026-09-14 β 2026-09-23 Β· 2 obs
β 2026-09-23 21:13:12
βNSns2fkr.name.com2026-09-14 β 2026-09-23 Β· 2 obs
β 2026-09-23 21:13:12
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| ptcms.dev | ns3npv.name.com, ns2fkr.name.com, ns4jpz.name.com, ns1bcp.name.com | - |
β Authoritative Response
Server:163.114.217.49
NS records: ns3npv.name.com, ns2fkr.name.com, ns4jpz.name.com, ns1bcp.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for ptcms.dev (unsigned zone)
β±οΈ Timing
Total: 600ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1bcp.name.com, ns2fkr.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
Name Servers
Five name servers handle delegation for ptcms.dev: ns1.name.com, ns1bcp.name.com, ns2fkr.name.com and two others.
ptcms.dev has at least partial name server overlap with other domains, such as queensviewtv.com, sentinelgraph.app, samehmshaly.com and two others.
ns3npv.name.com, ns4jpz.name.com and ns1hwy.name.com β plus 7 other name servers β are commonly paired with these name servers.
Host names pointing to two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1bcp.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2fkr.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3npv.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4jpz.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1bcp.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1bcp.name.com each resolve to 163.114.216.17 IP addresses.