tmsapi.com - dns.ninja
tmsapi.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=1786481794 | ||||||
Subdomains
developer.tmsapi.com |
data.tmsapi.com |
www.tmsapi.com |
Same first word
tmsapi.com |
Similar names
DNS History
10 records (10 active, 0 former)
●NSns-1521.awsdns-62.org2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●NSns-1705.awsdns-21.co.uk2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●NSns-4.awsdns-00.com2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●NSns-874.awsdns-45.net2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●MXalt1.aspmx.l.google.com2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●MXalt2.aspmx.l.google.com2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●MXaspmx.l.google.com2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●MXaspmx2.googlemail.com2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●MXaspmx3.googlemail.com2015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
●A207.7.131.2422015-08-17 → 2026-08-11 · 2 obs
● 2026-08-11 21:26:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net... | - |
| tmsapi.com | ns-4.awsdns-00.com, ns-874.awsdns-45.net, ns-1705.awsdns-21.co.uk, ns-1521.awsdns-62.org | 2 records |
✅ Authoritative Response
Server:205.251.198.169
NS records: ns-4.awsdns-00.com, ns-874.awsdns-45.net, ns-1705.awsdns-21.co.uk, ns-1521.awsdns-62.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tmsapi.com (unsigned zone)
⏱️ Timing
Total: 534ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 207.7.131.242 |
| NS | 4 | ns-1521.awsdns-62.org, ns-1705.awsdns-21.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 5 | _globalsign-domain-verification=8RD1hFKo, _globalsign-domain-verification=Bbo0vzRF... |
| SOA | 1 | ns-1521.awsdns-62.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-4.awsdns-00.com, ns-4.awsdns-00.com)
Analysis
Hierarchy
tmsapi.com is a parent domain, with developer.tmsapi.com, data.tmsapi.com and www.tmsapi.com beneath it.
IP Addresses
tmsapi.com points to a single IP number: 207.7.131.242.
Name Servers
tmsapi.com has four authoritative name servers: ns-4.awsdns-00.com, ns-874.awsdns-45.net, ns-1521.awsdns-62.org and ns-1705.awsdns-21.co.uk.
tmsapi.com has at least partial name server overlap with other domains, such as washingtonparentdeals.com, d3k49jb9bk37vi.cloudfront.net, commoditynewswires.com and two others.
ns-4.awsdns-00.com, ns-874.awsdns-45.net, ns-1521.awsdns-62.org and ns-1705.awsdns-21.co.uk all point to exactly two IP numbers each: ns-4.awsdns-00.com → 205.251.192.4 and 2600:9000:5300:400::1; ns-874.awsdns-45.net → 205.251.195.106 and 2600:9000:5303:6a00::1; ns-1521.awsdns-62.org → 205.251.197.241 and 2600:9000:5305:f100::1; ns-1705.awsdns-21.co.uk → 205.251.198.169 and 2600:9000:5306:a900::1.
Mail Servers
Mail for tmsapi.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
tmsapi.com shares mail servers — at least in part — with other domains, including ns500731.ns500671.ns500731.ns500688.ns500705.ns500705.ns500688.ns500291.ns500653.ns500153.tenderladiesbz.com, ns500698.ns500758.ns500758.ns500698.ns500736.ns500735.ns500698.ns500708.ns500708.ns500576.ns500686.ns500686.ns500652.ns500619.trackreceptor.com, ns500768.ns500698.ns500698.ns500698.ns500736.ns500736.ns500735.ns500735.ns500735.ns500735.ns500698.ns500576.ns500619.ns500698.ns500686.ns500652.trackreceptor.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.16.26 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.