protocolrecord.com - dns.ninja
protocolrecord.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 216.150.1.65🇨🇦 Amazon216.150.1.0/24 EC2 Prefix | ||||||
| A | 216.150.1.193🇨🇦 Amazon216.150.1.0/24 EC2 Prefix | ||||||
| NS | ns1.vercel-dns.com ⭐ | ||||||
| A | 2620:4d:4000:6259:7:13:0:1🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1 | ||||||
| PTR | dns1.p13.nsone.net | ||||||
| A | 198.51.44.13🇺🇸 NSONE198.51.44.0/24 | ||||||
| PTR | dns1.p13.nsone.net | ||||||
| NS | ns2.vercel-dns.com | ||||||
| A | 2a00:edc0:6259:7:13::2🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2 | ||||||
| PTR | dns2.p13.nsone.net | ||||||
| A | 198.51.45.13🇺🇸 NSONE198.51.45.0/24 | ||||||
| PTR | dns2.p13.nsone.net | ||||||
| SOA | ns1.vercel-dns.comhostmaster@nsone.net serial=1793086965 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1793607371 | ||||||
Same first word
protocolrecord.com |
Similar names
Previous names
Next names
DNS History
9 records (4 active, 5 former)
●NSns1.vercel-dns.com2026-10-27 → 2026-11-02 · 2 obs
● 2026-11-02 08:37:02
●NSns2.vercel-dns.com2026-10-27 → 2026-11-02 · 2 obs
● 2026-11-02 08:37:02
○A216.150.1.12026-10-31 → 2026-10-31 · 4 obs
● 2026-10-31 14:46:40
○ 2026-11-01 09:29:40
○ 2026-11-02 08:37:02
○A216.150.1.1292026-11-01 → 2026-11-01 · 4 obs
● 2026-11-01 09:29:40
○ 2026-11-02 05:20:38
○ 2026-11-02 08:37:02
●A216.150.1.1932026-11-02 → 2026-11-02 · 3 obs
● 2026-11-02 08:36:56
● 2026-11-02 08:37:02
●A216.150.1.652026-11-02 → 2026-11-02 · 3 obs
● 2026-11-02 08:36:56
● 2026-11-02 08:37:02
○A216.150.16.12026-10-27 → 2026-10-27 · 3 obs
○ 2026-10-31 14:46:40
○ 2026-11-02 08:37:02
○A216.150.16.1292026-10-31 → 2026-10-31 · 4 obs
● 2026-10-31 14:46:40
○ 2026-11-02 08:36:56
○ 2026-11-02 08:37:02
○A216.150.16.1932026-10-27 → 2026-11-02 · 5 obs
○ 2026-10-31 14:46:40
● 2026-11-02 05:20:38
○ 2026-11-02 08:36:56
○ 2026-11-02 08:37:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| protocolrecord.com | ns1.vercel-dns.com, ns2.vercel-dns.com | - |
✅ Authoritative Response
Server:198.51.44.13
NS records: ns1.vercel-dns.com, ns2.vercel-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for protocolrecord.com (unsigned zone)
⏱️ Timing
Total: 249ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 216.150.1.193, 216.150.1.1 |
| NS | 2 | ns1.vercel-dns.com, ns2.vercel-dns.com |
| SOA | 1 | ns1.vercel-dns.com hostmaster.nsone.net |
Analysis
IP Addresses
protocolrecord.com directs to two IP numbers, 216.150.1.65 and 216.150.1.193
fnfos.ai, ourslowboot.com, uplevelclub.com and two other host names share IP numbers with protocolrecord.com.
Name Servers
DNS delegation for protocolrecord.com points to two name servers: ns1.vercel-dns.com and ns2.vercel-dns.com.
protocolrecord.com uses the same name servers as several other domains — among them toprewardsource.com, digitaledge.site, imeniglass.com and two more.
protocolrecord.com has partial name server overlap with other domains, including anthonymlns.com.
ns1.vercel-dns.com directs to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1. ns2.vercel-dns.com directs to 198.51.45.13 and 2a00:edc0:6259:7:13::2. Each host name carries two IP addresses.