invaxis.com - robtex.com
invaxis.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 64.225.100.177🇩🇪 DIGITALOCEAN64.225.96.0/20 DigitalOcean | ||||||
| NS | ns1.invaxis.com ⭐ | ||||||
| A | 64.225.100.177🇩🇪 DIGITALOCEAN64.225.96.0/20 DigitalOcean | ||||||
| NS | ns2.invaxis.com | ||||||
| A | 64.225.100.177🇩🇪 DIGITALOCEAN64.225.96.0/20 DigitalOcean | ||||||
| MX | mail.invaxis.com ⭐ | ||||||
| A | 64.225.100.177🇩🇪 DIGITALOCEAN64.225.96.0/20 DigitalOcean | ||||||
| TXT | v=spf1 +a +mx +a:ip-172-26-5-140.eu-central-1.compute.internal -all | ||||||
| SOA | ns1.invaxis.comistanbouli@magton.com 2026-02-06 #1 | ||||||
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=1775062982 | ||||||
Subdomains
Same first word
invaxis.com |
Similar names
vinxisa.com |
invasix.co.uk |
invasix.be |
invasix.ru |
navixis.com |
invasix.ca |
nivaxis.com |
sivanix.com |
vinaxis.com |
invasix.com |
DNS History
22 records (4 active, 18 former)
○NSecn.invaxis.com2016-01-23 → 2016-09-17 · 5 obs
○ 2015-10-31 04:37:16
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
○ 2026-04-01 17:21:20
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
○ 2026-04-01 17:21:20
●NSns1.invaxis.com2026-03-12 → 2026-04-01 · 3 obs
○ 2017-10-01 13:25:36
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
●NSns2.invaxis.com2026-03-12 → 2026-04-01 · 3 obs
○ 2017-10-01 13:25:36
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
○NSns31.domaincontrol.com2017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○NSns32.domaincontrol.com2017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○NSns51.domaincontrol.com2015-06-19 → 2015-10-31 · 4 obs
● 2015-06-19 00:13:36
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
○NSns52.domaincontrol.com2015-06-19 → 2015-10-31 · 4 obs
● 2015-06-19 00:13:36
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
○NSrfa.invaxis.com2016-01-23 → 2016-09-17 · 5 obs
○ 2015-10-31 04:37:16
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
○ 2026-04-01 17:21:20
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
○ 2026-04-01 17:21:20
●MXmail.invaxis.com2016-01-23 → 2026-04-01 · 6 obs
○ 2015-10-31 04:37:16
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
○MXmailstore1.secureserver.net2015-06-19 → 2015-10-31 · 4 obs
● 2015-06-19 00:13:36
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
○MXsmtp.secureserver.net2015-06-19 → 2015-10-31 · 4 obs
● 2015-06-19 00:13:36
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
○A184.168.221.162017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A184.168.221.22017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A184.168.221.292017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A184.168.221.82017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A50.63.202.162017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A50.63.202.192017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A50.63.202.22017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A50.63.202.242017-10-01 → 2017-10-01 · 4 obs
○ 2016-09-17 17:36:40
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
● 2017-10-01 13:25:36
○ 2026-03-12 07:50:44
○ 2026-04-01 17:21:20
○A50.63.202.52015-06-19 → 2015-10-31 · 4 obs
● 2015-06-19 00:13:36
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
● 2015-10-31 04:37:16
○ 2016-01-23 19:59:18
○ 2026-04-01 17:21:20
○A52.28.90.1332016-01-23 → 2016-09-17 · 5 obs
○ 2015-10-31 04:37:16
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
○ 2026-04-01 17:21:20
● 2016-01-23 19:59:18
● 2016-09-17 17:36:40
○ 2017-10-01 13:25:36
○ 2026-04-01 17:21:20
●A64.225.100.1772026-03-12 → 2026-04-01 · 3 obs
○ 2017-10-01 13:25:36
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
● 2026-03-12 07:50:44
● 2026-04-01 17:21:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| invaxis.com | ns1.invaxis.com, ns2.invaxis.com | 2 records |
✅ Authoritative Response
Server:64.225.100.177
NS records: ns1.invaxis.com, ns2.invaxis.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for invaxis.com (unsigned zone)
⏱️ Timing
Total: 221ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 64.225.100.177 |
| NS | 2 | ns2.invaxis.com, ns1.invaxis.com |
| MX | 1 | mail.invaxis.com (pri: 10) |
| TXT | 1 | v=spf1 +a +mx +a:ip-172-26-5-140.eu-cent |
| SOA | 1 | ns1.invaxis.com istanbouli.magton.com |
📌 Glue Records Collected
Total: 2
In-bailiwick: 2 (ns1.invaxis.com, ns2.invaxis.com)
Analysis
Hierarchy
invaxis.com is a parent of ns1.invaxis.com, mail.invaxis.com and ns2.invaxis.com.
IP Addresses
invaxis.com resolves to a single IP address: 64.225.100.177.
Other host names including ns1.invaxis.com, ns2.lujainalbayat.com, ns2.ginses.com, mail.invaxis.com and mail.lujainalbayat.com share IP numbers with invaxis.com.
Name Servers
invaxis.com's delegation uses two name servers, ns1.invaxis.com and ns2.invaxis.com.
Host names with a single IP:
- ns1.invaxis.com points to 64.225.100.177
- ns2.invaxis.com points to 64.225.100.177
Host names that point to 64.225.100.177: ns1.invaxis.com and ns2.invaxis.com
Mail Servers
invaxis.com is handled by a single mail server, mail.invaxis.com.
mail.invaxis.com points to a single IP: 64.225.100.177.