sarumtech.com - dns.ninja

sarumtech.com

DNSSEC⚠️ Not signed
NSa.misconfigured.powerdns.server ⭐
NSa.pipe.co
A46.20.238.100🇬🇧 IOMART-AS46.20.224.0/20 Melbourne Originated Routes
PTRpurely.domains
NSb.pipe.co
A159.89.249.145🇬🇧 DIGITALOCEAN159.89.248.0/22 DigitalOcean
PTRb.pipe.co
SOAa.misconfigured.powerdns.serverhostmaster@sarumtech.com 2022-06-25 #5

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1785578887

Same first word

sarumtech.com

Similar names

masterchu.com.cn
amherstcu.net
teamcrush.com
surematch.org
surematch.co.uk
masterchu.cn
martechus.com
chatsumer.com
crushteam.com
crushmate.in
chartmuse.com
masterchu.com
marcusteh.com
meatcrush.com
themarcus.com
mustarche.com
chemastur.com
matchuser.com
chatsumer.app
crushmate.com
surmatech.com
mhauserct.com
chemstaru.com
mathcurse.com

DNS History

26 records (3 active, 23 former)

2017201820192020202120222023202420252026NSa.misconfigured.powerdns.servera.pipe.cob.pipe.coadi.ns.cloudflare.comarch.ns.cloudflare.comns-1321.awsdns-37.orgns-1586.awsdns-06.co.ukns-65.awsdns-08.comns-787.awsdns-34.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA104.24.102.143104.24.103.1432400:cb00:2048:1::6818:668f2400:cb00:2048:1::6818:678f52.218.144.752.218.144.9552.218.192.10752.218.192.1152.218.192.9154.231.168.18754.231.177.6754.231.184.247
●NSa.misconfigured.powerdns.server2026-02-22 → 2026-08-01 · 6 obs
○ 2017-11-01 15:27:04
● 2026-02-22 05:07:34
● 2026-04-19 15:24:50
○ 2026-06-06 08:57:52
● 2026-06-17 07:09:58
● 2026-08-01 10:20:34
●NSa.pipe.co2026-02-22 → 2026-08-01 · 3 obs
○ 2017-11-01 15:27:04
● 2026-02-22 05:07:34
● 2026-08-01 10:20:34
○NSadi.ns.cloudflare.com2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 02:21:46
○ 2017-11-01 15:27:04
○ 2026-08-01 10:20:34
○NSarch.ns.cloudflare.com2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 02:21:46
○ 2017-11-01 15:27:04
○ 2026-08-01 10:20:34
●NSb.pipe.co2026-02-22 → 2026-08-01 · 3 obs
○ 2017-11-01 15:27:04
● 2026-02-22 05:07:34
● 2026-08-01 10:20:34
○NSns-1321.awsdns-37.org2017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○NSns-1586.awsdns-06.co.uk2017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○NSns-65.awsdns-08.com2017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○NSns-787.awsdns-34.net2017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○MXalt1.aspmx.l.google.com2016-12-20 → 2017-11-01 · 4 obs
● 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○MXalt2.aspmx.l.google.com2016-12-20 → 2017-11-01 · 4 obs
● 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○MXalt3.aspmx.l.google.com2016-12-20 → 2017-11-01 · 4 obs
● 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○MXalt4.aspmx.l.google.com2016-12-20 → 2017-11-01 · 4 obs
● 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○MXaspmx.l.google.com2016-12-20 → 2017-11-01 · 4 obs
● 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A104.24.102.1432016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 02:21:46
○ 2017-11-01 15:27:04
○ 2026-08-01 10:20:34
○A104.24.103.1432016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 02:21:46
○ 2017-11-01 15:27:04
○ 2026-08-01 10:20:34
○A2400:cb00:2048:1::6818:668f2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 02:21:46
○ 2017-11-01 15:27:04
○ 2026-08-01 10:20:34
○A2400:cb00:2048:1::6818:678f2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 02:21:46
○ 2017-11-01 15:27:04
○ 2026-08-01 10:20:34
○A52.218.144.72017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A52.218.144.952017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A52.218.192.1072017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A52.218.192.112017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A52.218.192.912017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A54.231.168.1872017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A54.231.177.672017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34
○A54.231.184.2472017-11-01 → 2017-11-01 · 4 obs
○ 2016-12-20 02:21:46
● 2017-11-01 15:27:04
○ 2026-02-22 05:07:34
○ 2026-08-01 10:20:34

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comb.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, k.gtld-servers.net...-
sarumtech.coma.pipe.co, b.pipe.co-

✅ Authoritative Response

Server:159.89.249.145

NS records: a.pipe.co, b.pipe.co

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sarumtech.com (unsigned zone)

⏱️ Timing

Total: 950ms | Queries: -

📄 Records

TypeCountSample Data
NS2b.pipe.co, a.pipe.co
SOA1a.misconfigured.powerdns.server hostmast

Analysis

Name Servers

sarumtech.com is delegated to three name servers: a.pipe.co, b.pipe.co and a.misconfigured.powerdns.server.

The name servers of sarumtech.com overlap at least partially with those of other domains — among them homeclean.biz, ngn.au, 26.77.37.in-addr.arpa and two more.

These name servers commonly appear in delegations together with ns1.rgb365.eu, ns2.rgb365.eu, a.misconfigured.dns.server.invalid and 6 other.

Both a.pipe.co and b.pipe.co have a single IP address each — a.pipe.co resolves to 46.20.238.100 while b.pipe.co resolves to 159.89.249.145.