tapmark.dev - robtex.com
tapmark.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
Next names
tapngo.dev |
tapngoqr.dev |
tapninja.dev |
tapnomad.dev |
tapok.dev |
tapon.dev |
taponit.dev |
tapoos.dev |
tappa.dev |
tappable.dev |
tapparo.dev |
tappe.dev |
tapped.dev |
tappeer.dev |
tappengine.dev |
tappin.dev |
tappp.dev |
tappr.dev |
tapps.dev |
DNS History
5 records (5 active, 0 former)
βNSns1bcp.name.com2026-08-26 β 2026-09-19 Β· 2 obs
β 2026-09-19 23:23:28
βNSns2fjz.name.com2026-08-26 β 2026-09-19 Β· 2 obs
β 2026-09-19 23:23:28
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| tapmark.dev | ns3fhx.name.com, ns1bcp.name.com, ns2fjz.name.com, ns4fqz.name.com | - |
β Authoritative Response
Server:163.114.217.49
NS records: ns3fhx.name.com, ns1bcp.name.com, ns2fjz.name.com, ns4fqz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for tapmark.dev (unsigned zone)
β±οΈ Timing
Total: 878ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1bcp.name.com, ns2fjz.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
Name Servers
The authoritative name servers for tapmark.dev are ns1.name.com, ns1bcp.name.com, ns2fjz.name.com and two others.
tapmark.dev has at least partial name server overlap with other domains, such as almersal.org, continuumtrust.com, envelopeprogram.com and two others.
ns4fqz.name.com, ns3fhx.name.com and ns4ghm.name.com β plus 7 other name servers β are commonly paired with these name servers.
Hosts with two IP numbers each:
ns1.name.com maps to two IP addresses β 163.114.216.17 and 2a00:edc0:107::1.
ns1bcp.name.com maps to two IP addresses β 163.114.216.17 and 2a00:edc0:107::1.
ns2fjz.name.com maps to two IP addresses β 163.114.216.49 and 2402:cf80:107::1.
ns3fhx.name.com maps to two IP addresses β 163.114.217.17 and 2a00:edc0:107::49.
ns4fqz.name.com maps to two IP addresses β 163.114.217.49 and 2402:cf80:107::49.
These two host names β ns1.name.com and ns1bcp.name.com β each point to 2a00:edc0:107::1 IP addresses.
These two host names β ns1.name.com and ns1bcp.name.com β each point to 163.114.216.17 IP addresses.