pixel.qa - dns.ninja
pixel.qa
qa
| DNSSEC | ⚠️ Not signed | ||||||
| NS | e.registry.qa ⭐ | ||||||
| NS | a.registry.qa | ||||||
| NS | b.registry.qa | ||||||
| NS | c.registry.qa | ||||||
| NS | d.registry.qa | ||||||
| NS | f.registry.qa | ||||||
| NS | g.registry.qa | ||||||
| NS | h.registry.qa | ||||||
| NS | i.registry.qa | ||||||
| SOA | e.registry.qasend@mail.to.tech.at.domains.qa serial=2018275334 | ||||||
Same first word
Similar names
DNS History
11 records (6 active, 5 former)
○NSns1.bluehost.com2016-01-19 → 2017-01-10 · 4 obs
● 2017-01-10 08:00:48
○ 2026-03-19 04:04:06
○ 2026-08-17 03:07:52
●NSns1.routedge.net2026-03-19 → 2026-08-17 · 5 obs
● 2026-03-19 04:04:06
○ 2026-07-10 13:26:56
● 2026-08-15 07:22:58
● 2026-08-17 03:07:52
○NSns2.bluehost.com2016-01-19 → 2017-01-10 · 4 obs
● 2017-01-10 08:00:48
○ 2026-03-19 04:04:06
○ 2026-08-17 03:07:52
●NSns2.routedge.net2026-03-19 → 2026-08-17 · 5 obs
● 2026-03-19 04:04:06
○ 2026-07-10 13:26:56
● 2026-08-15 07:22:58
● 2026-08-17 03:07:52
○MXmail.pixel.qa2016-01-19 → 2017-01-10 · 4 obs
● 2017-01-10 08:00:48
○ 2026-03-19 04:04:06
○ 2026-08-17 03:07:52
●MXmx.zoho.com2026-03-19 → 2026-08-17 · 5 obs
● 2026-03-19 04:04:06
○ 2026-07-10 13:26:56
● 2026-08-15 07:22:58
● 2026-08-17 03:07:52
●MXmx2.zoho.com2026-03-19 → 2026-08-17 · 5 obs
● 2026-03-19 04:04:06
○ 2026-07-10 13:26:56
● 2026-08-15 07:22:58
● 2026-08-17 03:07:52
●MXmx3.zoho.com2026-03-19 → 2026-08-17 · 5 obs
● 2026-03-19 04:04:06
○ 2026-07-10 13:26:56
● 2026-08-15 07:22:58
● 2026-08-17 03:07:52
○A198.54.115.912026-03-19 → 2026-06-12 · 5 obs
● 2026-03-19 04:04:06
● 2026-06-12 16:56:08
○ 2026-07-09 19:02:58
○ 2026-08-17 03:07:52
●A198.54.116.2192026-07-09 → 2026-08-17 · 5 obs
● 2026-07-09 19:02:58
○ 2026-07-10 13:26:56
● 2026-08-15 07:22:58
● 2026-08-17 03:07:52
○A50.87.231.602016-01-19 → 2017-01-10 · 4 obs
● 2017-01-10 08:00:48
○ 2026-03-19 04:04:06
○ 2026-08-17 03:07:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| qa | g.registry.qa, i.registry.qa, a.registry.qa, e.registry.qa... | 13 records |
| pixel.qa | ns2.routedge.net, ns1.routedge.net | - |
✅ Authoritative Response
Server:185.136.99.202
NS records: ns2.routedge.net, ns1.routedge.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for qa (unsigned zone)
⏱️ Timing
Total: 4639ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.54.116.219 |
| NS | 2 | ns1.routedge.net, ns2.routedge.net |
| MX | 3 | mx.zoho.com (pri: 10), mx3.zoho.com (pri: 50)... |
| TXT | 2 | zoho-verification=zb81844517.zmverify.zo, v=spf1 include:zohomail.com ~all |
| SOA | 1 | ns1.routedge.net support.cloudns.net |
📌 Glue Records Collected
Total: 13
In-bailiwick: 13 (g.registry.qa, g.registry.qa, i.registry.qa...)
Analysis
IP Addresses
pixel.qa directs to one IP number, which is 198.54.116.219.
Among the host names that share IP numbers with pixel.qa are gestordeportivo.club, smallorgfundraising.com, server72-5.web-hosting.com and two others.
Name Servers
Two name servers handle the delegation for pixel.qa: ns1.routedge.net and ns2.routedge.net.
pixel.qa has the same name server delegation as a number of other domains, such as charterhouse.com.qa, hatco.com.qa, qatarinternationalmotorshow.gov.qa and two more.
pixel.qa partially shares its NS delegation with several other domains, including kidzania.qa, bradmagroup.com.qa, alemadistones.com and two others.
ns1.routedge.net resolves to 185.136.98.202. ns2.routedge.net resolves to 185.136.99.202. Both host names point to a single IP number.
Mail Servers
pixel.qa uses three mail servers — mx2.zoho.com, mx3.zoho.com and mx.zoho.com.
pixel.qa shares at least some of its mail servers with other domains — for example catole.com.br, imastudies.com, mordavid.ai and two more.
Each of mx2.zoho.com, mx3.zoho.com and mx.zoho.com resolves to one IP address: mx2.zoho.com to 136.143.183.44, and both mx3.zoho.com and mx.zoho.com to 204.141.43.44.
mx3.zoho.com along with mx.zoho.com each resolve to 204.141.43.44 IP addresses.