🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`podscriptom.com`

DNSSEC	⚠️ Not signed
A	92.53.96.117^{🇷🇺 TimeWeb-AS92.53.96.0/24}
		PTR	`bitrix404.timeweb.ru`
NS	`ns1.timeweb.ru` ⭐
		A	2a03:6f04:dead:bee::1^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	85.193.93.93^{🇵🇱 TimeWeb-AS85.193.93.0/24}
			PTR	`ns1.timeweb.ru`
NS	`ns2.timeweb.ru`
		A	2a03:6f04:dead:bee::2^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	85.193.93.85^{🇵🇱 TimeWeb-AS85.193.93.0/24}
			PTR	`ns2.timeweb.ru`
NS	`ns3.timeweb.org`
		A	2a03:6f07:4::2^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	217.78.234.130^{🇷🇺 TimeWeb-AS217.78.234.0/24}
NS	`ns4.timeweb.org`
		A	2a00:65e0:6:5:232a::2^{🇷🇺 RETNRU-SPB-AS2a00:65e0::/32 CJSC "RetnNet"}
		A	139.45.249.139^{🇷🇺 RETNRU-SPB-AS139.45.248.0/21 RETN-SPB}
			PTR	`gw-139.45.249.139-rt1.km.spb.retn.ru`
MX	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`v=spf1 redirect=_spf.yandex.net`
SOA	`ns1.timeweb.ru`dns@timeweb.ru 2025-09-22 #5

`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.net`nstld@verisign-grs.com serial=1791403274

Same first word

podscriptom.com

podscriptom.ru

Similar names

promptdisco.com

promptdisco.ai

discoprompt.com

Previous names

Next names

DNS History

16 records (6 active, 10 former)

○NSdns1.yandex.net2016-12-15 → 2017-02-16 · 4 obs

● 2016-12-15 09:41:14
● 2017-02-16 09:45:48
○ 2018-08-21 03:54:34
○ 2026-10-07 20:19:58

○NSdns2.yandex.net2017-02-16 → 2017-02-16 · 4 obs

○ 2016-12-15 09:41:14
● 2017-02-16 09:45:48
○ 2018-08-21 03:54:34
○ 2026-10-07 20:19:58

○NSns1.hostinger.ru2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 09:41:14
○ 2017-02-16 09:45:48
○ 2026-10-07 20:19:58

●NSns1.timeweb.ru2018-08-21 → 2026-10-07 · 3 obs

○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
● 2026-10-07 20:19:58

○NSns2.hostinger.ru2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 09:41:14
○ 2017-02-16 09:45:48
○ 2026-10-07 20:19:58

●NSns2.timeweb.ru2018-08-21 → 2026-10-07 · 3 obs

○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
● 2026-10-07 20:19:58

○NSns3.hostinger.ru2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 09:41:14
○ 2017-02-16 09:45:48
○ 2026-10-07 20:19:58

●NSns3.timeweb.org2018-08-21 → 2026-10-07 · 3 obs

○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
● 2026-10-07 20:19:58

○NSns4.hostinger.ru2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 09:41:14
○ 2017-02-16 09:45:48
○ 2026-10-07 20:19:58

●NSns4.timeweb.org2018-08-21 → 2026-10-07 · 3 obs

○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
● 2026-10-07 20:19:58

●MXmx.yandex.net2016-12-15 → 2026-10-07 · 4 obs

● 2016-12-15 09:41:14
○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
● 2026-10-07 20:19:58

○MXmx1.hostinger.ru2017-02-16 → 2017-02-16 · 4 obs

○ 2016-12-15 09:41:14
● 2017-02-16 09:45:48
○ 2018-08-21 03:54:34
○ 2026-10-07 20:19:58

○A2a03:6f00:1::5c35:60842018-08-21 → 2018-08-21 · 4 obs

○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
○ 2026-08-29 15:09:20
○ 2026-10-07 20:19:58

○A31.220.16.1592016-12-15 → 2017-02-16 · 4 obs

● 2016-12-15 09:41:14
● 2017-02-16 09:45:48
○ 2018-08-21 03:54:34
○ 2026-10-07 20:19:58

●A92.53.96.1172026-08-29 → 2026-10-07 · 3 obs

○ 2018-08-21 03:54:34
● 2026-08-29 15:09:20
● 2026-10-07 20:19:58

○A92.53.96.1322018-08-21 → 2018-08-21 · 4 obs

○ 2017-02-16 09:45:48
● 2018-08-21 03:54:34
○ 2026-08-29 15:09:20
○ 2026-10-07 20:19:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, m.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net...	-
podscriptom.com	ns1.timeweb.ru, ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org	-

✅ Authoritative Response

Server:139.45.249.139

NS records: ns1.timeweb.ru, ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for podscriptom.com (unsigned zone)

⏱️ Timing

Total: 1195ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`92.53.96.117`
NS	4	`ns4.timeweb.org, ns1.timeweb.ru...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`ns1.timeweb.ru dns.timeweb.ru`

Analysis

IP Addresses

podscriptom.com directs to one IP number, which is 92.53.96.117.

Among the host names that share IP numbers with podscriptom.com are cb83927.tw1.ru, opt-lider.ru, bio-him.spb.ru and two others.

Name Servers

The domain podscriptom.com is delegated to these four name servers: ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru and ns2.timeweb.ru.

podscriptom.com shares at least some of its name servers with other domains, including moepravo.org, mirxr.ru, supersro.ru and two others.

The host names ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru and ns2.timeweb.ru each resolve to two IP addresses: ns3.timeweb.org resolves to 217.78.234.130 and 2a03:6f07:4::2; ns4.timeweb.org resolves to 139.45.249.139 and 2a00:65e0:6:5:232a::2; ns1.timeweb.ru resolves to 85.193.93.93 and 2a03:6f04:dead:bee::1; ns2.timeweb.ru resolves to 85.193.93.85 and 2a03:6f04:dead:bee::2.

Mail Servers

podscriptom.com routes its mail through a single mail server, mx.yandex.net.

podscriptom.com has the same mail server arrangement as a number of other domains, for example mamaispekla.ru, xn----8sbflajc7cimdc1b4h.xn--p1ai, durag-icp.ru and two more.

mx.yandex.net points to two IP addresses: 77.88.21.249 and 2a02:6b8::311.

podscriptom.com - robtex.com

podscriptom.com

com

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`podscriptom.com`

`com`