inlancom.com - robtex.com
inlancom.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 172.234.24.211🇺🇸 AKAMAI-LINODE-AP172.234.16.0/20 Akamai Technologies | ||||||
| PTR | k8s-svc-lander-namecheap-expired-us-ord-02.parklogic.net | ||||||
| A | 172.239.57.117🇺🇸 AKAMAI-LINODE-AP172.239.32.0/19 Akamai Technologies | ||||||
| NS | dns101.registrar-servers.com ⭐ | ||||||
| A | 72.251.11.93🇨🇦 OVH72.251.0.0/17 Hosting route | ||||||
| PTR | ns5041709.ip-72-251-11.net | ||||||
| NS | dns102.registrar-servers.com | ||||||
| A | 72.251.11.125🇨🇦 OVH72.251.0.0/17 Hosting route | ||||||
| PTR | ns5028639.ip-72-251-11.net | ||||||
| MX | mx.plingest.com ⭐ | ||||||
| A | 38.143.66.193🇺🇸 AS6302338.143.66.0/24 Proxy-registered route object 2011686 | ||||||
| PTR | 193-66-143-38.clients.gthost.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | dns101.registrar-servers.comhostmaster@parklogic.com 2021-05-19 #1 | ||||||
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=1783621257 | ||||||
Same first word
inlancom.com |
Similar names
DNS History
11 records (5 active, 6 former)
●NSdns101.registrar-servers.com2026-03-03 → 2026-07-09 · 3 obs
● 2026-03-03 18:09:20
● 2026-07-09 18:44:10
●NSdns102.registrar-servers.com2026-03-03 → 2026-07-09 · 3 obs
● 2026-03-03 18:09:20
● 2026-07-09 18:44:10
○NSian.ns.cloudflare.com2020-01-01 → 2020-01-01 · 3 obs
○ 2026-03-03 18:09:20
○ 2026-07-09 18:44:10
○NSlily.ns.cloudflare.com2020-01-01 → 2020-01-01 · 3 obs
○ 2026-03-03 18:09:20
○ 2026-07-09 18:44:10
●MXmx.plingest.com2026-03-03 → 2026-07-09 · 2 obs
● 2026-07-09 18:44:10
○A104.27.188.782020-01-01 → 2020-01-01 · 3 obs
○ 2026-03-03 18:09:20
○ 2026-07-09 18:44:10
○A104.27.189.782020-01-01 → 2020-01-01 · 3 obs
○ 2026-03-03 18:09:20
○ 2026-07-09 18:44:10
●A172.234.24.2112026-03-03 → 2026-07-09 · 3 obs
● 2026-03-03 18:09:20
● 2026-07-09 18:44:10
●A172.239.57.1172026-03-03 → 2026-07-09 · 3 obs
● 2026-03-03 18:09:20
● 2026-07-09 18:44:10
○A2606:4700:30::681b:bc4e2020-01-01 → 2020-01-01 · 3 obs
○ 2026-03-03 18:09:20
○ 2026-07-09 18:44:10
○A2606:4700:30::681b:bd4e2020-01-01 → 2020-01-01 · 3 obs
○ 2026-03-03 18:09:20
○ 2026-07-09 18:44:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| inlancom.com | ns1.julydns.com, ns2.julydns.com | 2 records |
✅ Authoritative Response
Server:162.159.48.223
NS records: ns1.julydns.com, ns2.julydns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for inlancom.com (unsigned zone)
⏱️ Timing
Total: 378ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| CNAME | 1 | a.dnsapi12.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)
Analysis
IP Addresses
inlancom.com has two IP addresses: 172.234.24.211 and 172.239.57.117
Name Servers
inlancom.com is delegated to two name servers: dns101.registrar-servers.com and dns102.registrar-servers.com.
Both dns101.registrar-servers.com and dns102.registrar-servers.com have a single IP address each — dns101.registrar-servers.com resolves to 72.251.11.93 while dns102.registrar-servers.com resolves to 72.251.11.125.
Mail Servers
inlancom.com has one mail server: mx.plingest.com.
mx.plingest.com resolves to a single IP number: 38.143.66.193.