lancom.co - dns.ninja
lancom.co
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.afternic.com ⭐ | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| NS | ns2.afternic.com | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.afternic.comdns@jomax.net serial=1 | ||||||
co
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.registrydns.co | ||||||
| NS | b.registrydns.co | ||||||
| NS | c.registrydns.co | ||||||
| NS | d.registrydns.co | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1759691968 | ||||||
Same first word
Similar names
DNS History
19 records (4 active, 15 former)
○NSlaunch1.spaceship.net2026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 05:38:00
○ 2026-05-13 03:26:14
○ 2026-06-27 11:05:54
○NSlaunch2.spaceship.net2026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 05:38:00
○ 2026-05-13 03:26:14
○ 2026-06-27 11:05:54
●NSns1.afternic.com2026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 11:05:54
○NSns1.atom.com2026-05-13 → 2026-05-13 · 4 obs
● 2026-05-13 03:26:14
● 2026-05-13 22:25:38
○ 2026-06-27 11:05:54
●NSns2.afternic.com2026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 11:05:54
○NSns2.atom.com2026-05-13 → 2026-05-13 · 4 obs
● 2026-05-13 03:26:14
● 2026-05-13 22:25:38
○ 2026-06-27 11:05:54
○NSns75.domaincontrol.com2015-08-15 → 2026-03-07 · 4 obs
● 2026-03-07 18:12:54
○ 2026-04-09 10:04:16
○ 2026-06-27 11:05:54
○NSns76.domaincontrol.com2015-08-15 → 2026-03-07 · 4 obs
● 2026-03-07 18:12:54
○ 2026-04-09 10:04:16
○ 2026-06-27 11:05:54
○NSverification-3r3ipgtgwhs8zwpdevae45.ns101.verify.hn2026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 05:38:00
○ 2026-05-13 03:26:14
○ 2026-06-27 11:05:54
○MXmailstore1.secureserver.net2015-08-15 → 2026-03-07 · 4 obs
● 2026-03-07 18:12:54
○ 2026-04-09 10:04:16
○ 2026-06-27 11:05:54
○MXsmtp.secureserver.net2015-08-15 → 2026-03-07 · 4 obs
● 2026-03-07 18:12:54
○ 2026-04-09 10:04:16
○ 2026-06-27 11:05:54
●A13.248.169.482026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 11:05:54
○A13.248.213.452026-03-07 → 2026-03-07 · 4 obs
● 2026-03-07 18:12:54
○ 2026-04-09 10:04:16
○ 2026-06-27 11:05:54
○A44.232.173.2492026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 05:38:00
○ 2026-05-13 03:26:14
○ 2026-06-27 11:05:54
○A50.63.202.42015-08-15 → 2017-02-18 · 4 obs
● 2017-02-18 12:24:32
○ 2026-03-07 18:12:54
○ 2026-06-27 11:05:54
○A52.20.84.622026-05-13 → 2026-05-13 · 4 obs
● 2026-05-13 03:26:14
● 2026-05-13 22:25:38
○ 2026-06-27 11:05:54
○A52.40.42.1132026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 05:38:00
○ 2026-05-13 03:26:14
○ 2026-06-27 11:05:54
●A76.223.54.1462026-06-27 → 2026-06-27 · 2 obs
● 2026-06-27 11:05:54
○A76.223.67.1892026-03-07 → 2026-03-07 · 4 obs
● 2026-03-07 18:12:54
○ 2026-04-09 10:04:16
○ 2026-06-27 11:05:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| co | a.registrydns.co, d.registrydns.co, c.registrydns.co, b.registrydns.co | - |
| lancom.co | ns2.afternic.com, ns1.afternic.com | - |
✅ Authoritative Response
Server:97.74.98.69
NS records: ns2.afternic.com, ns1.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for lancom.co (unsigned zone)
⏱️ Timing
Total: 450ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.afternic.com dns.jomax.net |
Analysis
IP Addresses
lancom.co points to the IP addresses 13.248.169.48 and 76.223.54.146
Additional host names — mail.marketinglive.com, qnltd.com, afritz.com and two others — share IP numbers with lancom.co.
Name Servers
lancom.co has two authoritative name servers — ns1.afternic.com and ns2.afternic.com.
lancom.co shares its name server setup with other domains, including efware.com, qm23.com, bv.ws and two others.
The name servers of lancom.co overlap at least partially with those of other domains — among them regaldynasty.com, sgcol.com, voltgenerator.com and two more.
The name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn, verification-ag3xtxqjhqhiyarqdrht2l.ns101.verify.hn and verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn are commonly seen alongside these name servers.
Both ns1.afternic.com and ns2.afternic.com have two IP addresses each. ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45; ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45.