looool.com - robtex.com
looool.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.45.246.141🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094 | ||||||
| NS | ns1.domainrecover.com ⭐ | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns2.domainrecover.com | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| PTR | 199.247.16.62.vultrusercontent.com | ||||||
| TXT | yGjyZf7SHD | ||||||
| SOA | ns1.domainrecover.comhostmaster@domainreover.com serial=1623031840 | ||||||
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=1790935439 | ||||||
Same first word
Similar names
Previous names
looons.com |
looons404.com |
looony.com |
loooo.com |
loooob.com |
looooc.com |
loooof.com |
loooofiii.com |
loooog.com |
loooogd.com |
looooge.com |
looooi.com |
looook.com |
looooka.com |
looookbaby.com |
looooker.com |
looookey.com |
looooks.com |
Next names
DNS History
10 records (3 active, 7 former)
●NSns1.domainrecover.com2026-09-10 → 2026-10-02 · 3 obs
● 2026-09-10 14:54:40
● 2026-10-02 10:32:04
○NSns1.dsredirection.com2015-10-17 → 2016-03-24 · 4 obs
● 2016-03-24 18:42:46
○ 2017-02-01 10:54:56
○ 2026-10-02 10:32:04
●NSns2.domainrecover.com2026-09-10 → 2026-10-02 · 3 obs
● 2026-09-10 14:54:40
● 2026-10-02 10:32:04
○NSns2.dsredirection.com2015-10-17 → 2016-03-24 · 4 obs
● 2016-03-24 18:42:46
○ 2017-02-01 10:54:56
○ 2026-10-02 10:32:04
○MXmxs1.domainrecover.com2015-08-14 → 2017-02-01 · 4 obs
● 2017-02-01 10:54:56
○ 2026-09-10 14:54:40
○ 2026-10-02 10:32:04
○MXmxs2.domainrecover.com2015-08-14 → 2017-02-01 · 4 obs
● 2017-02-01 10:54:56
○ 2026-09-10 14:54:40
○ 2026-10-02 10:32:04
○A141.8.230.202015-08-14 → 2017-02-01 · 4 obs
● 2017-02-01 10:54:56
○ 2026-09-10 14:54:40
○ 2026-10-02 10:32:04
●A66.45.246.1412026-09-10 → 2026-10-02 · 3 obs
● 2026-09-10 14:54:40
● 2026-10-02 10:32:04
○CNAMEpres.serverhome.com2015-08-14 → 2017-02-01 · 4 obs
● 2017-02-01 10:54:56
○ 2026-09-10 14:54:40
○ 2026-10-02 10:32:04
○CNAMEthie5ku9.dsgeneration.com2015-10-17 → 2016-03-24 · 5 obs
● 2015-10-17 17:44:44
● 2016-03-24 18:42:46
○ 2017-02-01 10:54:56
○ 2026-10-02 10:32:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| looool.com | ns1.domainrecover.com, ns2.domainrecover.com | 2 records |
✅ Authoritative Response
Server:149.248.38.58
NS records: ns1.domainrecover.com, ns2.domainrecover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for looool.com (unsigned zone)
⏱️ Timing
Total: 797ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.45.246.141 |
| NS | 2 | NS2.DOMAINRECOVER.com, NS1.DOMAINRECOVER.com |
| TXT | 1 | yGjyZf7SHD |
| SOA | 1 | ns1.domainrecover.com hostmaster.domainr |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)
Analysis
IP Addresses
looool.com has exactly one IP address — 66.45.246.141.
lineline.com, haiten.com, ip-software.com plus two other host names have IP numbers in common with looool.com.
Name Servers
The NS records for looool.com delegate to ns1.domainrecover.com and ns2.domainrecover.com.
The name server configuration of looool.com is shared with other domains, for instance afalon.com, itgraf.com, charityreport.com and two others.
looool.com partially shares its NS delegation with several other domains, including buduaar.com, icupon.com, cortivo.com and two others.
These name servers tend to appear together with the name servers ns1.serverhome.com, ns2.serverhome.com and ns2.servering.com, plus two others.
ns1.domainrecover.com resolves to 149.248.38.58. ns2.domainrecover.com resolves to 199.247.16.62. Both host names point to a single IP number.