realapy.com - dns.ninja
realapy.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=1782641745 | ||||||
Same first word
realapy.com |
Similar names
DNS History
5 records (4 active, 1 former)
●NSns1.p02.dynect.net2015-07-04 → 2026-06-28 · 2 obs
● 2026-06-28 10:23:16
●NSns2.p02.dynect.net2015-07-04 → 2026-06-28 · 2 obs
● 2026-06-28 10:23:16
●NSns3.p02.dynect.net2015-07-04 → 2026-06-28 · 2 obs
● 2026-06-28 10:23:16
●NSns4.p02.dynect.net2015-07-04 → 2026-06-28 · 2 obs
● 2026-06-28 10:23:16
○A72.32.155.2152015-07-04 → 2020-01-05 · 4 obs
● 2020-01-05 04:07:46
○ 2026-06-07 05:32:20
○ 2026-06-28 10:23:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| realapy.com | ns1.p02.dynect.net, ns3.p02.dynect.net, ns2.p02.dynect.net, ns4.p02.dynect.net | - |
✅ Authoritative Response
Server:108.59.166.202
NS records: ns1.p02.dynect.net, ns3.p02.dynect.net, ns2.p02.dynect.net, ns4.p02.dynect.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for realapy.com (unsigned zone)
⏱️ Timing
Total: 1738ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The NS records for realapy.com point to four name servers: ns1.p02.dynect.net, ns2.p02.dynect.net, ns3.p02.dynect.net and ns4.p02.dynect.net.
realapy.com has at least partial name server overlap with other domains, such as bestsocalhomesearch.com, mycarolinasrealestate.com, explorewilmingtonhomes.net and two others.
It is common to find these name servers paired with the name servers ns1.p68.dns.oraclecloud.net, ns2.p68.dns.oraclecloud.net, ns3.p68.dns.oraclecloud.net and ns4.p68.dns.oraclecloud.net.
ns1.p02.dynect.net, ns2.p02.dynect.net, ns3.p02.dynect.net and ns4.p02.dynect.net all point to exactly two IP numbers each: ns1.p02.dynect.net → 108.59.166.202 and 2600:2000:2100::ca; ns2.p02.dynect.net → 108.59.168.202 and 2600:2000:2110::ca; ns3.p02.dynect.net → 108.59.170.202 and 2600:2000:2120::ca; ns4.p02.dynect.net → 108.59.172.202 and 2600:2000:2130::ca.