force-am.com - dns.ninja
force-am.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=1783977822 | ||||||
Same first word
force-am.com |
Similar names
DNS History
22 records (11 active, 11 former)
○NSdns1.name-services.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○NSdns2.name-services.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○NSdns3.name-services.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○NSdns4.name-services.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○NSdns5.name-services.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
●NSns1.xserver.jp2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●NSns2.xserver.jp2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●NSns3.xserver.jp2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●NSns4.xserver.jp2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●NSns5.xserver.jp2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●MXalt1.aspmx.l.google.com2016-12-15 → 2026-07-13 · 2 obs
● 2026-07-13 21:53:02
●MXalt2.aspmx.l.google.com2016-12-15 → 2026-07-13 · 2 obs
● 2026-07-13 21:53:02
●MXalt3.aspmx.l.google.com2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●MXalt4.aspmx.l.google.com2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
●MXaspmx.l.google.com2016-12-15 → 2026-07-13 · 2 obs
● 2026-07-13 21:53:02
○MXaspmx2.googlemail.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○MXaspmx3.googlemail.com2016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
●A157.112.183.1542026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 21:54:26
● 2026-07-13 21:53:02
○A216.239.32.212016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○A216.239.34.212016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○A216.239.36.212016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
○A216.239.38.212016-12-15 → 2017-12-23 · 4 obs
● 2017-12-23 12:20:06
○ 2026-03-26 21:54:26
○ 2026-07-13 21:53:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| force-am.com | ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp... | - |
✅ Authoritative Response
Server:35.72.43.26
NS records: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for force-am.com (unsigned zone)
⏱️ Timing
Total: 2327ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 157.112.183.154 |
| NS | 5 | ns1.xserver.jp, ns5.xserver.jp... |
| MX | 5 | alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 +a:sv5313.xserver.jp +a:force-am. |
| SOA | 1 | ns1.xserver.jp root.xserver.jp |
Analysis
IP Addresses
force-am.com has exactly one IP address — 157.112.183.154.
mb.hiurahp-nurse.jp, sclinic.jp, mail.zabonchan.com plus two other host names have IP numbers in common with force-am.com.
Name Servers
Five name servers handle delegation for force-am.com: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp and two others.
There is at least partial name server overlap between force-am.com and other domains — hamichan.com, lifedesignedit.com, etoile-kaito.com and two more among them.
These name servers frequently co-occur with the name servers ns4.xserver.jp and ns5.xserver.jp.
Host names carrying three IP numbers:
ns1.xserver.jp resolves to three addresses: 202.226.36.164, 202.226.36.170 and 202.226.36.246.
ns4.xserver.jp resolves to three addresses: 183.90.224.226, 183.90.224.230 and 202.226.39.247.
ns5.xserver.jp resolves to three addresses: 157.112.182.218, 157.112.182.220 and 202.226.37.247.
Host names resolving to a single IP address:
ns2.xserver.jp points to the IP address 35.72.43.26.
ns3.xserver.jp points to the IP address 202.226.36.247.
Mail Servers
Five mail servers handle force-am.com: 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 force-am.com are shared with other domains: laurinburgchamber.com, homesafetyprofessionals.com, ns500734.ns500734.ns500693.ns500699.ns500699.ns500693.ns500588.ns500588.ns500683.ns500588.ns500632.ns500588.ns500112.dtrkdll.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com maps to two IP addresses — 172.253.139.26 and 2607:f8b0:4004:c09::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.27 and 2a00:1450:400c:c23::1b.