nosp.in - robtex.com
nosp.in
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns000.ns0.com ⚠️ Not in zone NS records | ||||||
| A | 216.92.61.61🇺🇸 AS7859216.92.0.0/16 Pair Networks, Inc. 2403 Sidney St. STE 210 Pittsburgh, PA 15203 | ||||||
| PTR | ns000.ns0.com | ||||||
| NS | ns61.pair.com ⚠️ Not in zone NS records | ||||||
| A | 209.68.1.131🇺🇸 AS7859209.68.0.0/18 | ||||||
| PTR | roomen.pair.com | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1785327355 | ||||||
Same first word
Similar names
DNS History
9 records (2 active, 7 former)
●NSns000.ns0.com2026-05-18 → 2026-07-29 · 5 obs
○ 2017-06-04 13:06:52
● 2026-05-18 08:14:32
○ 2026-07-02 18:54:02
● 2026-07-12 04:29:24
● 2026-07-29 12:52:34
● 2026-05-18 08:14:32
○ 2026-07-02 18:54:02
● 2026-07-12 04:29:24
● 2026-07-29 12:52:34
○NSns1.101domain.com2015-07-11 → 2017-06-04 · 4 obs
● 2015-07-11 00:55:40
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
○NSns2.101domain.com2015-07-11 → 2017-06-04 · 4 obs
● 2015-07-11 00:55:40
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
○NSns5.101domain.com2015-07-11 → 2017-06-04 · 4 obs
● 2015-07-11 00:55:40
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
●NSns61.pair.com2026-05-18 → 2026-07-29 · 3 obs
○ 2017-06-04 13:06:52
● 2026-05-18 08:14:32
● 2026-07-29 12:52:34
● 2026-05-18 08:14:32
● 2026-07-29 12:52:34
○MXmail.101domain.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-10-07 21:47:28
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
○MXmail.rwgusa.net2015-07-11 → 2016-10-07 · 4 obs
● 2015-07-11 00:55:40
● 2016-10-07 21:47:28
○ 2017-06-04 13:06:52
○ 2026-07-29 12:52:34
● 2016-10-07 21:47:28
○ 2017-06-04 13:06:52
○ 2026-07-29 12:52:34
○A199.73.55.482017-06-04 → 2017-06-04 · 4 obs
○ 2016-10-07 21:47:28
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
● 2017-06-04 13:06:52
○ 2026-05-18 08:14:32
○ 2026-07-29 12:52:34
○A66.240.194.1392015-07-11 → 2016-10-07 · 4 obs
● 2015-07-11 00:55:40
● 2016-10-07 21:47:28
○ 2017-06-04 13:06:52
○ 2026-07-29 12:52:34
● 2016-10-07 21:47:28
○ 2017-06-04 13:06:52
○ 2026-07-29 12:52:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns2.registry.in, ns1.registry.in, ns4.registry.in, ns3.registry.in | - |
| nosp.in | ns61.pair.com, ns000.ns0.com | - |
✅ Authoritative Response
Server:209.68.1.131
NS records: ns61.pair.com, ns000.ns0.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for nosp.in (unsigned zone)
⏱️ Timing
Total: 559ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
nosp.in has two authoritative name servers — ns000.ns0.com and ns61.pair.com.
nosp.in shares at least some of its name servers with other domains, including algordon.com, mackarch.com, devilsfoot.com and two others.
These name servers are frequently seen alongside ns553.pair.com, ns560.pair.com, ns528.pair.com and 7 other name servers.
ns000.ns0.com and ns61.pair.com each resolve to one IP number: ns000.ns0.com points to 216.92.61.61 and ns61.pair.com points to 209.68.1.131.