riodating.com - dns.ninja
riodating.com
| DNSSEC | β οΈ Not signed | ||||||
| A | 13.248.169.48πΊπΈ Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146πΊπΈ Amazon76.223.48.0/20 | ||||||
| NS | ns2.afternic.com β | ||||||
| A | 2603:5:2226::45πΊπΈ GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69πΊπΈ GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| NS | ns1.afternic.com | ||||||
| A | 2603:5:2126::45πΊπΈ GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69πΊπΈ GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns2.afternic.comdns@jomax.net serial=1 | ||||||
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=1785468477 | ||||||
Subdomains
redbussecondarydns.riodating.com |
redbusprimarydns.riodating.com |
Same first word
riodating.com |
Similar names
DNS History
15 records (4 active, 11 former)
βNSdns101.registrar-servers.com2026-03-29 β 2026-04-14 Β· 5 obs
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βNSdns102.registrar-servers.com2026-03-29 β 2026-04-14 Β· 5 obs
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βNSns1.afternic.com2026-02-27 β 2026-07-31 Β· 7 obs
β 2026-02-27 05:53:22
β 2026-03-16 13:57:50
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βNSns2.afternic.com2026-02-27 β 2026-07-31 Β· 7 obs
β 2026-02-27 05:53:22
β 2026-03-16 13:57:50
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βNSredbusprimarydns.riodating.com2015-06-16 β 2018-06-27 Β· 4 obs
β 2018-06-27 03:59:54
β 2026-02-27 05:53:22
β 2026-07-31 03:56:32
βNSredbussecondarydns.riodating.com2015-06-16 β 2018-06-27 Β· 4 obs
β 2018-06-27 03:59:54
β 2026-02-27 05:53:22
β 2026-07-31 03:56:32
βMXmx.plingest.com2026-03-29 β 2026-04-14 Β· 4 obs
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βA13.248.169.482026-02-27 β 2026-07-31 Β· 7 obs
β 2026-02-27 05:53:22
β 2026-03-16 13:57:50
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βA172.234.24.2112026-03-29 β 2026-04-14 Β· 5 obs
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βA172.239.57.1172026-03-29 β 2026-04-14 Β· 5 obs
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
βA195.149.84.1002015-06-16 β 2018-06-27 Β· 4 obs
β 2018-06-27 03:59:54
β 2026-02-27 05:53:22
β 2026-07-31 03:56:32
βA195.149.84.1012015-06-16 β 2018-06-27 Β· 4 obs
β 2018-06-27 03:59:54
β 2026-02-27 05:53:22
β 2026-07-31 03:56:32
βA2001:67c:38c::642015-06-16 β 2018-06-27 Β· 4 obs
β 2018-06-27 03:59:54
β 2026-02-27 05:53:22
β 2026-07-31 03:56:32
βA2001:67c:38c::652015-06-16 β 2018-06-27 Β· 4 obs
β 2018-06-27 03:59:54
β 2026-02-27 05:53:22
β 2026-07-31 03:56:32
βA76.223.54.1462026-02-27 β 2026-07-31 Β· 7 obs
β 2026-02-27 05:53:22
β 2026-03-16 13:57:50
β 2026-03-29 00:52:14
β 2026-04-14 11:14:12
β 2026-05-16 04:42:30
β 2026-07-31 03:56:32
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| riodating.com | ns1.afternic.com, ns2.afternic.com | 4 records |
β Authoritative Response
Server:173.201.66.69
NS records: ns1.afternic.com, ns2.afternic.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for riodating.com (unsigned zone)
β±οΈ Timing
Total: 1659ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns2.afternic.com dns.jomax.net |
π Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)
Analysis
Hierarchy
riodating.com serves as the parent of redbussecondarydns.riodating.com and redbusprimarydns.riodating.com.
IP Addresses
riodating.com directs to two IP numbers, 13.248.169.48 and 76.223.54.146
094hh.com, sunshineshipping.com, mail.puntodegiro.com plus two other host names have IP numbers in common with riodating.com.
Name Servers
DNS delegation for riodating.com points to two name servers: ns1.afternic.com and ns2.afternic.com.
The name server configuration of riodating.com is shared with other domains, for instance lasvegastrailerrental.com, mail.darkwasp.com, s1.afterburnabs.com and two others.
riodating.com shares at least some of its name servers with other domains, including dagof.com, drankin.com, inclusivefoods.com and two others.
These name servers are frequently seen alongside verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-urj2ap2akmgcchkhharttb.ns101.verify.hn, verification-iryqusbri9xlks4ssi7d4w.ns101.verify.hn and 3 other name servers.
ns1.afternic.com directs to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com directs to 173.201.66.69 and 2603:5:2226::45. Each host name carries two IP addresses.