ingeksa.com - dns.ninja
ingeksa.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=1783200816 | ||||||
Same first word
ingeksa.com |
Similar names
DNS History
15 records (10 active, 5 former)
○NShidden-master.yahoo.com2015-05-31 → 2017-11-16 · 4 obs
● 2017-11-16 22:47:00
○ 2026-02-14 19:46:48
○ 2026-07-04 21:49:40
●NSns-cloud-e1.googledomains.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●NSns-cloud-e2.googledomains.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●NSns-cloud-e3.googledomains.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●NSns-cloud-e4.googledomains.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
○NSyns1.yahoo.com2015-05-31 → 2017-11-16 · 4 obs
● 2017-11-16 22:47:00
○ 2026-02-14 19:46:48
○ 2026-07-04 21:49:40
○NSyns2.yahoo.com2015-05-31 → 2017-11-16 · 4 obs
● 2017-11-16 22:47:00
○ 2026-02-14 19:46:48
○ 2026-07-04 21:49:40
●MXalt1.aspmx.l.google.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●MXalt2.aspmx.l.google.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●MXalt3.aspmx.l.google.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●MXalt4.aspmx.l.google.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
●MXaspmx.l.google.com2026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
○MXmx-biz.mail.am0.yahoodns.net2015-05-31 → 2017-11-16 · 4 obs
● 2017-11-16 22:47:00
○ 2026-02-14 19:46:48
○ 2026-07-04 21:49:40
●A198.185.159.1442026-02-14 → 2026-07-04 · 3 obs
● 2026-02-14 19:46:48
● 2026-07-04 21:49:40
○A98.138.19.1432015-05-31 → 2017-11-16 · 4 obs
● 2017-11-16 22:47:00
○ 2026-02-14 19:46:48
○ 2026-07-04 21:49:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, m.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net... | - |
| ingeksa.com | ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.34.110
NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 729ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.185.159.144 |
| NS | 4 | ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)
Analysis
IP Addresses
ingeksa.com resolves to just one IP address, 198.185.159.144.
Two other host names, along with workingrams.com, courageit.com and boomernationexpo.com, also share IP numbers with ingeksa.com.
Name Servers
The NS records for ingeksa.com point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
ingeksa.com has at least partial name server overlap with other domains, such as greatratenate.com, juliegenet.com, nicolasyan.com and two others.
It is common to see these name servers used together with name servers ns1.mirusresearch.com and ns2.mir.us.
ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.
Mail Servers
Mail for ingeksa.com is handled by five mail servers, namely 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 ingeksa.com and other domains, including ns500731.ns500671.ns500671.ns500742.ns500731.ns500754.ns500688.ns500678.ns500153.tenderladiesbz.com, ns500731.ns500742.ns500731.ns500742.ns500704.ns500704.ns500731.ns500731.ns500731.ns500731.ns500705.ns500671.ns500705.ns500688.ns500671.ns500666.tenderladiesbz.com, ns500698.ns500759.ns500698.ns500758.ns500698.ns500736.ns500735.ns500708.ns500735.ns500698.ns500576.ns500576.ns500576.ns500652.ns500619.ns500619.trackreceptor.com and two others.
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.
Host names that have two IP addresses:
aspmx.l.google.com has two IP addresses: 64.233.180.27 and 2607:f8b0:4004:c1f::1b.
alt1.aspmx.l.google.com has two IP addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com has two IP addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com has two IP addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com has two IP addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.