loopay.com - dns.ninja
loopay.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=1782752351 | ||||||
Same first word
loopay.com |
Similar names
DNS History
17 records (10 active, 7 former)
●NSns-1166.awsdns-17.org2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●NSns-1572.awsdns-04.co.uk2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●NSns-359.awsdns-44.com2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●NSns-602.awsdns-11.net2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
○NSns1.parkingcrew.net2015-06-23 → 2017-10-08 · 5 obs
● 2015-06-23 11:49:14
● 2017-10-08 12:23:16
○ 2026-02-14 19:11:22
○ 2026-06-29 17:13:26
○NSns2.parkingcrew.net2015-06-23 → 2017-10-08 · 5 obs
● 2015-06-23 11:49:14
● 2017-10-08 12:23:16
○ 2026-02-14 19:11:22
○ 2026-06-29 17:13:26
●MXalt1.aspmx.l.google.com2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●MXalt2.aspmx.l.google.com2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●MXalt3.aspmx.l.google.com2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●MXalt4.aspmx.l.google.com2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
●MXaspmx.l.google.com2026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
○MXmail.h-email.net2015-06-23 → 2016-07-22 · 5 obs
● 2015-06-23 11:49:14
● 2016-07-22 09:33:50
○ 2026-02-14 19:11:22
○ 2026-06-29 17:13:26
○A185.53.178.82017-10-08 → 2017-10-08 · 4 obs
● 2017-10-08 12:23:16
○ 2026-02-14 19:11:22
○ 2026-06-29 17:13:26
○A185.53.179.72015-06-23 → 2016-07-22 · 8 obs
● 2015-06-23 11:49:14
● 2015-11-12 21:34:06
○ 2016-02-02 00:46:50
● 2016-07-05 18:11:46
● 2016-07-22 09:33:50
○ 2017-10-08 12:23:16
○ 2026-06-29 17:13:26
○A185.53.179.92016-02-02 → 2016-02-02 · 4 obs
● 2016-02-02 00:46:50
○ 2016-07-05 18:11:46
○ 2026-06-29 17:13:26
●A54.160.212.1682026-02-14 → 2026-06-29 · 3 obs
● 2026-02-14 19:11:22
● 2026-06-29 17:13:26
○A54.72.9.512017-10-08 → 2017-10-08 · 4 obs
● 2017-10-08 12:23:16
○ 2026-02-14 19:11:22
○ 2026-06-29 17:13:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| loopay.com | ns-602.awsdns-11.net, ns-359.awsdns-44.com, ns-1572.awsdns-04.co.uk, ns-1166.awsdns-17.org | 2 records |
✅ Authoritative Response
Server:205.251.198.36
NS records: ns-602.awsdns-11.net, ns-359.awsdns-44.com, ns-1572.awsdns-04.co.uk, ns-1166.awsdns-17.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for loopay.com (unsigned zone)
⏱️ Timing
Total: 863ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.160.212.168 |
| NS | 4 | ns-1166.awsdns-17.org, ns-1572.awsdns-04.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | google-site-verification=AMPP5WgsVztMg0P, google-site-verification=O2o_b2Yhd_XK97J... |
| SOA | 1 | ns-1572.awsdns-04.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-359.awsdns-44.com, ns-359.awsdns-44.com)
Analysis
IP Addresses
loopay.com resolves to just one IP address, 54.160.212.168.
ec2-54-160-212-168.compute-1.amazonaws.com is an example of another host name that shares IP numbers with loopay.com.
Name Servers
The NS records for loopay.com point to four name servers: ns-359.awsdns-44.com, ns-602.awsdns-11.net, ns-1166.awsdns-17.org and ns-1572.awsdns-04.co.uk.
loopay.com shares at least some of its name servers with other domains, including chipax.com, peg.gd, universityobgynassoc.com and two others.
These name servers are frequently paired with the name servers ns-262.awsdns-32.com, ns-1461.awsdns-54.org and ns-1770.awsdns-29.co.uk.
The host names ns-359.awsdns-44.com, ns-602.awsdns-11.net, ns-1166.awsdns-17.org and ns-1572.awsdns-04.co.uk each resolve to two IP addresses: ns-359.awsdns-44.com resolves to 205.251.193.103 and 2600:9000:5301:6700::1; ns-602.awsdns-11.net resolves to 205.251.194.90 and 2600:9000:5302:5a00::1; ns-1166.awsdns-17.org resolves to 205.251.196.142 and 2600:9000:5304:8e00::1; ns-1572.awsdns-04.co.uk resolves to 205.251.198.36 and 2600:9000:5306:2400::1.
Mail Servers
loopay.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between loopay.com and other domains, including ns500768.ns500758.ns500759.ns500758.ns500736.ns500736.ns500736.ns500736.ns500698.ns500698.ns500698.ns500708.ns500652.ns500619.ns500619.trackreceptor.com, ns500599.ns500737.ns500724.ns500599.ns500724.ns500724.ns500583.ns500697.ns500682.ns500583.www.yummyflingsfinder.com, ns500699.ns500734.ns500693.ns500734.ns500734.ns500734.ns500683.ns500693.ns500632.ns500588.ns500588.ns500632.ns500612.ns500612.ns500110.dtrkdll.com and two others.
These mail servers tend to appear in combination with mail servers alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to 173.194.45.26 and 2607:f8b0:4004:c0b::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.