transmitsecurity.net - dns.ninja
transmitsecurity.net
net
| 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=1783164271 | ||||||
Same first word
transmitsecurity.net |
transmitsecurity.io |
transmitsecurity.com |
DNS History
15 records (10 active, 5 former)
●NSns-1318.awsdns-36.org2026-02-18 → 2026-07-04 · 3 obs
● 2026-02-18 20:28:52
● 2026-07-04 11:51:12
●NSns-1776.awsdns-30.co.uk2026-02-18 → 2026-07-04 · 3 obs
● 2026-02-18 20:28:52
● 2026-07-04 11:51:12
●NSns-470.awsdns-58.com2026-02-18 → 2026-07-04 · 3 obs
● 2026-02-18 20:28:52
● 2026-07-04 11:51:12
●NSns-543.awsdns-03.net2026-02-18 → 2026-07-04 · 3 obs
● 2026-02-18 20:28:52
● 2026-07-04 11:51:12
○NSns1.digitalocean.com2015-07-16 → 2017-04-09 · 4 obs
● 2017-04-09 09:42:42
○ 2026-02-18 20:28:52
○ 2026-07-04 11:51:12
○NSns2.digitalocean.com2015-07-16 → 2017-04-09 · 4 obs
● 2017-04-09 09:42:42
○ 2026-02-18 20:28:52
○ 2026-07-04 11:51:12
○NSns3.digitalocean.com2015-07-16 → 2017-04-09 · 4 obs
● 2017-04-09 09:42:42
○ 2026-02-18 20:28:52
○ 2026-07-04 11:51:12
●MXalt1.aspmx.l.google.com2015-07-16 → 2026-07-04 · 2 obs
● 2026-07-04 11:51:12
●MXalt2.aspmx.l.google.com2015-07-16 → 2026-07-04 · 2 obs
● 2026-07-04 11:51:12
●MXalt3.aspmx.l.google.com2026-02-18 → 2026-07-04 · 3 obs
● 2026-02-18 20:28:52
● 2026-07-04 11:51:12
●MXalt4.aspmx.l.google.com2026-02-18 → 2026-07-04 · 3 obs
● 2026-02-18 20:28:52
● 2026-07-04 11:51:12
●MXaspmx.l.google.com2015-07-16 → 2026-07-04 · 2 obs
● 2026-07-04 11:51:12
○MXaspmx2.googlemail.com2015-07-16 → 2017-04-09 · 4 obs
● 2017-04-09 09:42:42
○ 2026-02-18 20:28:52
○ 2026-07-04 11:51:12
○MXaspmx3.googlemail.com2015-07-16 → 2017-04-09 · 4 obs
● 2017-04-09 09:42:42
○ 2026-02-18 20:28:52
○ 2026-07-04 11:51:12
●A162.243.66.1452015-07-16 → 2026-07-04 · 2 obs
● 2026-07-04 11:51:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| transmitsecurity.net | ns-543.awsdns-03.net, ns-470.awsdns-58.com, ns-1776.awsdns-30.co.uk, ns-1318.awsdns-36.org | 2 records |
✅ Authoritative Response
Server:205.251.197.38
NS records: ns-543.awsdns-03.net, ns-470.awsdns-58.com, ns-1776.awsdns-30.co.uk, ns-1318.awsdns-36.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for transmitsecurity.net (unsigned zone)
⏱️ Timing
Total: 773ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.243.66.145 |
| NS | 4 | ns-1318.awsdns-36.org, ns-1776.awsdns-30.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | 0ed1fe018a923dcc609d87438393d016, google-site-verification=5lkmYXDQjbyIPMM... |
| SOA | 1 | ns-1776.awsdns-30.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-543.awsdns-03.net, ns-543.awsdns-03.net)
Analysis
IP Addresses
transmitsecurity.net directs to one IP number, which is 162.243.66.145.
Name Servers
The domain transmitsecurity.net is delegated to these four name servers: ns-470.awsdns-58.com, ns-543.awsdns-03.net, ns-1318.awsdns-36.org and ns-1776.awsdns-30.co.uk.
At least some of transmitsecurity.net's name servers are shared with other domains, for example facedata.com, msciap01.auth0.com, wildiaries.com and two more.
It is common for these name servers to be used in conjunction with the name servers ns-124.awsdns-15.com, ns-1216.awsdns-24.org and ns-1838.awsdns-37.co.uk.
Four hostnames, each resolving to a pair of IP addresses: ns-470.awsdns-58.com directs to 205.251.193.214 and 2600:9000:5301:d600::1; ns-543.awsdns-03.net directs to 205.251.194.31 and 2600:9000:5302:1f00::1; ns-1318.awsdns-36.org directs to 205.251.197.38 and 2600:9000:5305:2600::1; ns-1776.awsdns-30.co.uk directs to 205.251.198.240 and 2600:9000:5306:f000::1.
Mail Servers
transmitsecurity.net has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
transmitsecurity.net shares at least some of its mail servers with other domains — for example ns500698.ns500759.ns500758.ns500698.ns500736.ns500698.ns500698.ns500735.ns500735.ns500735.ns500708.ns500619.ns500619.ns500576.trackreceptor.com, ns500765.ns500699.ns500693.ns500693.ns500734.ns500588.ns500699.ns500693.ns500699.ns500632.ns500632.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500599.ns500599.ns500599.ns500599.ns500724.ns500737.ns500737.ns500724.ns500599.ns500737.ns500583.ns500583.ns500697.ns500697.ns500599.yummyflingsfinder.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 142.250.31.26 and 2607:f8b0:4004:c21::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
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.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.