laforceweb.com - dns.ninja
laforceweb.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=1785600807 | ||||||
Same first word
laforceweb.com |
DNS History
17 records (8 active, 9 former)
●NSdns1.registrar-servers.com2016-01-01 → 2026-08-01 · 3 obs
● 2016-01-01 08:37:00
● 2026-08-01 16:14:16
●NSdns2.registrar-servers.com2016-01-01 → 2026-08-01 · 3 obs
● 2016-01-01 08:37:00
● 2026-08-01 16:14:16
○NSdns3.registrar-servers.com2016-01-01 → 2017-03-22 · 5 obs
● 2016-01-01 08:37:00
● 2017-03-22 20:31:50
○ 2026-03-26 21:11:00
○ 2026-08-01 16:14:16
○NSdns4.registrar-servers.com2016-01-01 → 2017-03-22 · 5 obs
● 2016-01-01 08:37:00
● 2017-03-22 20:31:50
○ 2026-03-26 21:11:00
○ 2026-08-01 16:14:16
○NSdns5.registrar-servers.com2016-01-01 → 2017-03-22 · 5 obs
● 2016-01-01 08:37:00
● 2017-03-22 20:31:50
○ 2026-03-26 21:11:00
○ 2026-08-01 16:14:16
○NSns07.domaincontrol.com2015-06-03 → 2015-10-18 · 4 obs
● 2015-10-18 23:55:44
○ 2016-01-01 08:37:00
○ 2026-08-01 16:14:16
○NSns08.domaincontrol.com2015-06-03 → 2015-10-18 · 4 obs
● 2015-10-18 23:55:44
○ 2016-01-01 08:37:00
○ 2026-08-01 16:14:16
●MXalt1.aspmx.l.google.com2015-06-03 → 2026-08-01 · 2 obs
● 2026-08-01 16:14:16
●MXalt2.aspmx.l.google.com2015-06-03 → 2026-08-01 · 2 obs
● 2026-08-01 16:14:16
●MXalt3.aspmx.l.google.com2016-01-01 → 2026-08-01 · 3 obs
● 2016-01-01 08:37:00
● 2026-08-01 16:14:16
●MXalt4.aspmx.l.google.com2016-01-01 → 2026-08-01 · 3 obs
● 2016-01-01 08:37:00
● 2026-08-01 16:14:16
●MXaspmx.l.google.com2015-06-03 → 2026-08-01 · 2 obs
● 2026-08-01 16:14:16
○MXaspmx2.googlemail.com2015-06-03 → 2015-10-18 · 4 obs
● 2015-10-18 23:55:44
○ 2016-01-01 08:37:00
○ 2026-08-01 16:14:16
○MXaspmx3.googlemail.com2015-06-03 → 2015-10-18 · 4 obs
● 2015-10-18 23:55:44
○ 2016-01-01 08:37:00
○ 2026-08-01 16:14:16
○A184.168.221.302015-10-18 → 2015-10-18 · 4 obs
● 2015-10-18 23:55:44
○ 2016-01-01 08:37:00
○ 2026-08-01 16:14:16
●A31.170.160.932016-01-01 → 2026-08-01 · 3 obs
● 2016-01-01 08:37:00
● 2026-08-01 16:14:16
○A97.74.215.1572015-06-03 → 2015-06-03 · 3 obs
○ 2015-10-18 23:55:44
○ 2026-08-01 16:14:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| laforceweb.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for laforceweb.com (unsigned zone)
⏱️ Timing
Total: 148ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 31.170.160.93 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
laforceweb.com directs to one IP number, which is 31.170.160.93.
akeysoft.com, for instance, is one of the other host names sharing IP numbers with laforceweb.com.
Name Servers
laforceweb.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
laforceweb.com has the same name server delegation as a number of other domains, such as power-slots.com, transassoccol.com, aurantis.com and two more.
laforceweb.com shares at least some of its name servers with other domains, including charlie-dog-art.com, lannandaddy.com, huskerlawyer.com and two others.
These name servers are frequently paired with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
laforceweb.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
laforceweb.com shares at least some of its mail servers with other domains — for example teensvillerecords.com, ns500758.ns500698.ns500698.ns500758.ns500735.ns500735.ns500736.ns500698.ns500698.ns500576.ns500576.ns500619.ns500652.ns500576.trackreceptor.com, ns500759.ns500698.ns500736.ns500735.ns500736.ns500698.ns500736.ns500736.ns500708.ns500576.ns500698.ns500698.ns500619.ns500686.ns500619.ns500619.trackreceptor.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 172.253.115.26 and 2607:f8b0:4004:c17::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
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.27 and 2a00:1450:400c:c23::1a.