trafficengine.net - dns.ninja
trafficengine.net
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2001:41d0:203:2302:14e1:ef42:7ed5:4e65🇫🇷 OVH2001:41d0::/32 IPv6 | ||||||
| NS | dns.trafficengine.net ⭐ | ||||||
| A | 2001:41d0:203:2302:14e1:ef42:7ed5:4e65🇫🇷 OVH2001:41d0::/32 IPv6 | ||||||
| NS | ns1.trafficengine.net | ||||||
| NS | ns2.trafficengine.net | ||||||
| MX | mx.trafficengine.net ⭐ | ||||||
| A | 2001:41d0:203:2302:14e1:ef42:7ed5:4e65🇫🇷 OVH2001:41d0::/32 IPv6 | ||||||
| TXT | v=spf1 a:dns.trafficengine.net ~all | ||||||
| SOA | dns.trafficengine.netsupport@trafficengine.net 2011-11-20 #74 | ||||||
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=1785939384 | ||||||
Subdomains
Same first word
trafficengine.net |
trafficengine.com |
trafficengine.click |
DNS History
24 records (5 active, 19 former)
●NSdns.trafficengine.net2026-06-23 → 2026-08-05 · 3 obs
○ 2026-05-08 14:36:34
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
○NSdns101.registrar-servers.com2026-02-15 → 2026-02-15 · 4 obs
○ 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
○NSdns102.registrar-servers.com2026-02-15 → 2026-02-15 · 4 obs
○ 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
●NSns1.trafficengine.net2007-08-14 → 2026-08-05 · 5 obs
● 2007-08-14 17:51:52
○ 2015-08-09 08:12:46
○ 2026-05-08 14:36:34
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
○ 2015-08-09 08:12:46
○ 2026-05-08 14:36:34
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
○NSns15.domaincontrol.com2019-04-08 → 2026-02-15 · 5 obs
○ 2017-02-14 21:01:32
● 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
○NSns16.domaincontrol.com2019-04-08 → 2026-02-15 · 5 obs
○ 2017-02-14 21:01:32
● 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
●NSns2.trafficengine.net2026-06-23 → 2026-08-05 · 3 obs
○ 2026-05-08 14:36:34
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
○NSns37.domaincontrol.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○NSns38.domaincontrol.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○MXalt1.aspmx.l.google.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○MXalt2.aspmx.l.google.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○MXaspmx.l.google.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○MXaspmx2.googlemail.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○MXaspmx3.googlemail.com2015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○MXmx.plingest.com2026-02-15 → 2026-02-15 · 4 obs
○ 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
●MXmx.trafficengine.net2026-06-23 → 2026-08-05 · 3 obs
○ 2026-03-22 18:58:30
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
○MXtrafficengine.net.bak-mx.smtproutes.com2007-08-14 → 2007-08-14 · 3 obs
● 2007-08-14 17:51:52
○ 2015-08-09 08:12:46
○ 2026-08-05 14:27:30
○ 2015-08-09 08:12:46
○ 2026-08-05 14:27:30
○MXtrafficengine.net.pri-mx.smtproutes.com2007-08-14 → 2007-08-14 · 3 obs
● 2007-08-14 17:51:52
○ 2015-08-09 08:12:46
○ 2026-08-05 14:27:30
○ 2015-08-09 08:12:46
○ 2026-08-05 14:27:30
○A107.170.124.842015-08-09 → 2017-02-14 · 5 obs
○ 2007-08-14 17:51:52
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
● 2015-08-09 08:12:46
● 2017-02-14 21:01:32
○ 2019-04-08 17:06:16
○ 2026-08-05 14:27:30
○A172.234.24.2112026-02-15 → 2026-02-15 · 4 obs
○ 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
○A172.239.57.1172026-02-15 → 2026-02-15 · 4 obs
○ 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
●A2001:41d0:203:2302:14e1:ef42:7ed5:4e652026-06-23 → 2026-08-05 · 3 obs
○ 2026-03-22 18:58:30
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
● 2026-06-23 12:50:24
● 2026-08-05 14:27:30
○A216.246.127.122007-08-14 → 2007-08-14 · 3 obs
● 2007-08-14 17:51:52
○ 2015-08-09 08:12:46
○ 2026-08-05 14:27:30
○ 2015-08-09 08:12:46
○ 2026-08-05 14:27:30
○A50.63.202.732019-04-08 → 2026-02-15 · 5 obs
○ 2017-02-14 21:01:32
● 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
● 2019-04-08 17:06:16
● 2026-02-15 18:43:26
○ 2026-03-22 18:58:30
○ 2026-08-05 14:27:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| trafficengine.net | ns1.trafficengine.net, ns2.trafficengine.net | 2 records |
✅ Authoritative Response
Server:5.135.31.124
NS records: ns1.trafficengine.net, ns2.trafficengine.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trafficengine.net (unsigned zone)
⏱️ Timing
Total: 475ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| AAAA | 1 | 2001:41d0:203:2302:14e1:ef42:7ed5:4e65 |
| NS | 2 | ns2.trafficengine.net, ns1.trafficengine.net |
| MX | 1 | mx.trafficengine.net (pri: 0) |
| TXT | 1 | v=spf1 a:dns.trafficengine.net ~all |
| SOA | 1 | dns.trafficengine.net support.trafficeng |
📌 Glue Records Collected
Total: 2
In-bailiwick: 2 (ns1.trafficengine.net, ns2.trafficengine.net)
Analysis
Hierarchy
ns1.trafficengine.net, dns.trafficengine.net, mx.trafficengine.net and ns2.trafficengine.net each fall under the parent domain trafficengine.net.
IP Addresses
trafficengine.net resolves to one IP address: 2001:41d0:203:2302:14e1:ef42:7ed5:4e65.
dns.trafficengine.net and mx.trafficengine.net, along with other host names, share IP addresses with trafficengine.net.
Name Servers
DNS for trafficengine.net is handled by three authoritative name servers: dns.trafficengine.net, ns1.trafficengine.net and ns2.trafficengine.net.
Hosts with just one IP address:
dns.trafficengine.net directs to 2001:41d0:203:2302:14e1:ef42:7ed5:4e65.
Mail Servers
Mail for trafficengine.net is handled by a single mail server, mx.trafficengine.net.
mx.trafficengine.net has exactly one IP number: 2001:41d0:203:2302:14e1:ef42:7ed5:4e65.