q4api.com - dns.ninja
q4api.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=1781594425 | ||||||
Subdomains
dev.q4api.com |
Same first word
q4api.com |
Similar names
DNS History
9 records (9 active, 0 former)
●NSns-1217.awsdns-24.org2017-05-10 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●NSns-1923.awsdns-48.co.uk2017-05-10 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●NSns-358.awsdns-44.com2017-05-10 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●NSns-933.awsdns-52.net2017-05-10 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●MXalt1.aspmx.l.google.com2026-03-30 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●MXalt2.aspmx.l.google.com2026-03-30 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●MXalt3.aspmx.l.google.com2026-03-30 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●MXalt4.aspmx.l.google.com2026-03-30 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
●MXaspmx.l.google.com2026-03-30 → 2026-06-16 · 2 obs
● 2026-06-16 07:25:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, j.gtld-servers.net... | - |
| q4api.com | ns-358.awsdns-44.com, ns-933.awsdns-52.net, ns-1217.awsdns-24.org, ns-1923.awsdns-48.co.uk | 2 records |
✅ Authoritative Response
Server:205.251.196.193
NS records: ns-358.awsdns-44.com, ns-933.awsdns-52.net, ns-1217.awsdns-24.org, ns-1923.awsdns-48.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for q4api.com (unsigned zone)
⏱️ Timing
Total: 1943ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1217.awsdns-24.org, ns-1923.awsdns-48.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=xaNGfWjMNwzIZnk, v=spf1 -all |
| SOA | 1 | ns-1217.awsdns-24.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-358.awsdns-44.com, ns-358.awsdns-44.com)
Analysis
Hierarchy
dev.q4api.com is a subdomain of q4api.com.
Name Servers
Four name servers handle the delegation for q4api.com: ns-358.awsdns-44.com, ns-933.awsdns-52.net, ns-1217.awsdns-24.org and ns-1923.awsdns-48.co.uk.
The name servers of q4api.com overlap at least partially with those of other domains — among them grayston.net, tactful.ai, sandc.com.au and two more.
Each of the four hosts ns-358.awsdns-44.com, ns-933.awsdns-52.net, ns-1217.awsdns-24.org and ns-1923.awsdns-48.co.uk has two IP addresses. ns-358.awsdns-44.com points to 205.251.193.102 and 2600:9000:5301:6600::1. ns-933.awsdns-52.net points to 205.251.195.165 and 2600:9000:5303:a500::1. ns-1217.awsdns-24.org points to 205.251.196.193 and 2600:9000:5304:c100::1. ns-1923.awsdns-48.co.uk points to 205.251.199.131 and 2600:9000:5307:8300::1.
Mail Servers
q4api.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by q4api.com are shared with other domains: no.ca, ns500821.ns500794.ns500841.ns500795.ns500795.ns500794.ns500794.ns500795.ns500794.ns500821.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500821.ns500794.ns500794.ns500841.ns500821.ns500794.ns500821.ns500794.ns500821.ns500795.ns500821.ns500794.ns500821.ns500795.ns500795.lustypartnersfinder.com and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.