sanvert.com - dns.ninja
sanvert.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 159.89.244.183🇺🇸 DIGITALOCEAN159.89.244.0/22 DigitalOcean | ||||||
| A | 164.90.244.158🇺🇸 DIGITALOCEAN164.90.244.0/22 DigitalOcean | ||||||
| NS | ns1.perfectdomain.com ⚠️ Not in zone NS records | ||||||
| A | 159.89.244.183🇺🇸 DIGITALOCEAN159.89.244.0/22 DigitalOcean | ||||||
| NS | ns2.perfectdomain.com ⚠️ Not in zone NS records | ||||||
| A | 164.90.244.158🇺🇸 DIGITALOCEAN164.90.244.0/22 DigitalOcean | ||||||
| TXT | v=spf1 -all | ||||||
| TXT | v=DMARC1; p=reject; adkim=s; aspf=s; | ||||||
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=1782376845 | ||||||
Same first word
Similar names
DNS History
24 records (4 active, 20 former)
○NSf1g1ns1.dnspod.net2015-06-25 → 2015-10-18 · 4 obs
● 2015-10-18 04:47:46
○ 2016-03-30 10:32:36
○ 2026-06-25 08:55:34
○NSf1g1ns2.dnspod.net2015-10-18 → 2015-10-18 · 4 obs
● 2015-10-18 04:47:46
○ 2016-03-30 10:32:36
○ 2026-06-25 08:55:34
○NSns1.namebrightdns.com2016-03-30 → 2017-02-11 · 5 obs
● 2016-03-30 10:32:36
● 2017-02-11 20:33:02
○ 2020-03-08 14:37:12
○ 2026-06-25 08:55:34
●NSns1.perfectdomain.com2026-05-30 → 2026-06-25 · 3 obs
● 2026-05-30 14:43:18
● 2026-06-25 08:55:34
○NSns2.namebrightdns.com2016-04-13 → 2017-02-11 · 5 obs
● 2016-04-13 03:57:32
● 2017-02-11 20:33:02
○ 2020-03-08 14:37:12
○ 2026-06-25 08:55:34
●NSns2.perfectdomain.com2026-05-30 → 2026-06-25 · 3 obs
● 2026-05-30 14:43:18
● 2026-06-25 08:55:34
○NSnsg1.namebrightdns.com2016-03-30 → 2020-03-08 · 7 obs
● 2016-03-30 10:32:36
○ 2016-04-13 03:57:32
○ 2017-02-11 20:33:02
● 2020-03-08 14:37:12
○ 2026-03-27 12:29:58
○ 2026-06-25 08:55:34
○NSnsg2.namebrightdns.com2016-03-30 → 2020-03-08 · 7 obs
● 2016-03-30 10:32:36
○ 2016-04-13 03:57:32
○ 2017-02-11 20:33:02
● 2020-03-08 14:37:12
○ 2026-03-27 12:29:58
○ 2026-06-25 08:55:34
○NSsk.s5.ans1.ns148.ztomy.com2026-03-27 → 2026-04-13 · 5 obs
● 2026-03-27 12:29:58
● 2026-04-13 15:41:44
○ 2026-05-30 14:43:18
○ 2026-06-25 08:55:34
○NSsk.s5.ans2.ns148.ztomy.com2026-03-27 → 2026-04-13 · 5 obs
● 2026-03-27 12:29:58
● 2026-04-13 15:41:44
○ 2026-05-30 14:43:18
○ 2026-06-25 08:55:34
○MX~2026-03-27 → 2026-04-13 · 4 obs
● 2026-04-13 15:41:44
○ 2026-05-30 14:43:18
○ 2026-06-25 08:55:34
○A107.21.42.1422016-03-30 → 2016-03-30 · 4 obs
● 2016-03-30 10:32:36
○ 2016-04-13 03:57:32
○ 2026-06-25 08:55:34
○A127.0.0.12016-01-05 → 2016-01-05 · 3 obs
○ 2016-03-30 10:32:36
○ 2026-06-25 08:55:34
●A159.89.244.1832026-05-30 → 2026-06-25 · 3 obs
● 2026-05-30 14:43:18
● 2026-06-25 08:55:34
●A164.90.244.1582026-05-30 → 2026-06-25 · 3 obs
● 2026-05-30 14:43:18
● 2026-06-25 08:55:34
○A208.91.197.462026-03-27 → 2026-04-13 · 5 obs
● 2026-03-27 12:29:58
● 2026-04-13 15:41:44
○ 2026-05-30 14:43:18
○ 2026-06-25 08:55:34
○A34.199.151.1632017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 20:33:02
○ 2020-03-08 14:37:12
○ 2026-06-25 08:55:34
○A52.20.154.32017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 20:33:02
○ 2020-03-08 14:37:12
○ 2026-06-25 08:55:34
○A52.200.243.1232016-04-13 → 2016-04-13 · 4 obs
● 2016-04-13 03:57:32
○ 2017-02-11 20:33:02
○ 2026-06-25 08:55:34
○A54.152.144.2432016-04-13 → 2016-04-13 · 4 obs
● 2016-04-13 03:57:32
○ 2017-02-11 20:33:02
○ 2026-06-25 08:55:34
○A54.174.149.302016-03-30 → 2016-03-30 · 4 obs
● 2016-03-30 10:32:36
○ 2016-04-13 03:57:32
○ 2026-06-25 08:55:34
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2016-03-30 → 2016-04-13 · 4 obs
● 2016-04-13 03:57:32
○ 2017-02-11 20:33:02
○ 2026-06-25 08:55:34
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 20:33:02
○ 2020-03-08 14:37:12
○ 2026-06-25 08:55:34
○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2020-03-08 → 2020-03-08 · 4 obs
● 2020-03-08 14:37:12
○ 2026-03-27 12:29:58
○ 2026-06-25 08:55:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net... | - |
| sanvert.com | ns1.perfectdomain.com, ns2.perfectdomain.com | 2 records |
✅ Authoritative Response
Server:164.90.244.158
NS records: ns1.perfectdomain.com, ns2.perfectdomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sanvert.com (unsigned zone)
⏱️ Timing
Total: 2072ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 164.90.244.158, 159.89.244.183 |
| TXT | 2 | v=DMARC1; p=reject; adkim=s; aspf=s;, v=spf1 -all |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.perfectdomain.com, ns2.perfectdomain.com)
Analysis
IP Addresses
sanvert.com has two IP addresses: 159.89.244.183 and 164.90.244.158
Additional host names — mext.com, dsl022.swansea-council.diogel.com, humansmart.com and two others — share IP numbers with sanvert.com.
Name Servers
sanvert.com is served by two delegated name servers, ns1.perfectdomain.com and ns2.perfectdomain.com.
sanvert.com shares its name server setup with other domains, including wbhealth.com, digitalvip.com, wordi.com and two others.
ns1.perfectdomain.com → 159.89.244.183 and ns2.perfectdomain.com → 164.90.244.158: one IP number per host name.