rptracking.com - dns.ninja
rptracking.com
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=1783234236 | ||||||
Same first word
rptracking.com |
Similar names
DNS History
9 records (6 active, 3 former)
●NSns1-35.azure-dns.com2026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 07:12:38
○NSns1.tulsaconnect.com2019-12-15 → 2019-12-15 · 2 obs
○ 2026-07-05 07:12:38
●NSns2-35.azure-dns.net2026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 07:12:38
○NSns2.tulsaconnect.com2019-12-15 → 2019-12-15 · 2 obs
○ 2026-07-05 07:12:38
●NSns3-35.azure-dns.org2026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 07:12:38
●NSns4-35.azure-dns.info2026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 07:12:38
●MXrptracking-com.mail.protection.outlook.com2019-12-15 → 2026-07-05 · 2 obs
● 2026-07-05 07:12:38
●A20.168.50.1942026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 07:12:38
○A65.38.18.192019-12-15 → 2019-12-15 · 2 obs
○ 2026-07-05 07:12:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| rptracking.com | ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info | 2 records |
✅ Authoritative Response
Server:150.171.16.35
NS records: ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rptracking.com (unsigned zone)
⏱️ Timing
Total: 122ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 20.168.50.194 |
| NS | 4 | ns1-35.azure-dns.com, ns2-35.azure-dns.net... |
| MX | 1 | rptracking-com.mail.protection.outlook.c |
| TXT | 1 | v=spf1 ip4:65.38.18.9 include:spf.protec |
| SOA | 1 | ns1-35.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-35.azure-dns.com, ns1-35.azure-dns.com)
Analysis
IP Addresses
rptracking.com directs to one IP number, which is 20.168.50.194.
Among the host names that share IP numbers with rptracking.com are procalonline.com, maxpanda.net, maintenancepartner.net and two others.
Name Servers
The domain rptracking.com is delegated to these four name servers: ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org.
There is at least partial name server overlap between rptracking.com and other domains — runhappy.com, sirthomaslipton.jp, absatellite.net and two more among them.
All four hostnames — ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org — resolve to two IP numbers apiece: ns1-35.azure-dns.com to 150.171.10.35 and 2603:1061:0:10::23; ns4-35.azure-dns.info to 13.107.206.35 and 2620:1ec:bda:10::23; ns2-35.azure-dns.net to 150.171.16.35 and 2620:1ec:8ec:10::23; ns3-35.azure-dns.org to 13.107.222.35 and 2a01:111:4000:10::23.
Mail Servers
rptracking.com routes its mail through a single mail server, rptracking-com.mail.protection.outlook.com.
rptracking-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.10.2, 52.101.10.6 and 52.101.41.4, along with 5 other.