pythonrush.com - dns.ninja

πŸ›‘οΈDomain Reputation CheckBlocklist, phishing & malware statusβ†’

pythonrush.com

com

Same first word

Previous names

Next names

DNS History

25 records (4 active, 21 former)

2020202120222023202420252026NSns1.afternic.comns2.afternic.comns1.gm111.parklogic.comns1.parklogic.comns2.gm111.parklogic.comns2.parklogic.comns45.domaincontrol.comns46.domaincontrol.comMXmx156.hostedmxserver.comA13.248.169.4876.223.54.146172.233.219.123172.233.219.49172.233.219.78172.237.146.25172.237.146.38172.237.146.8184.168.221.41184.168.221.45184.168.221.52184.168.221.60184.168.221.61184.168.221.6250.63.202.4850.63.202.52
●NSns1.afternic.com2026-08-22 β†’ 2026-08-23 Β· 3 obs
β—‹ 2026-05-18 05:49:22
● 2026-08-22 07:27:30
● 2026-08-23 09:49:36
β—‹NSns1.gm111.parklogic.com2026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹NSns1.parklogic.com2026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
●NSns2.afternic.com2026-08-22 β†’ 2026-08-23 Β· 3 obs
β—‹ 2026-05-18 05:49:22
● 2026-08-22 07:27:30
● 2026-08-23 09:49:36
β—‹NSns2.gm111.parklogic.com2026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹NSns2.parklogic.com2026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹NSns45.domaincontrol.com2019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹NSns46.domaincontrol.com2019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹MXmx156.hostedmxserver.com2026-05-04 β†’ 2026-05-04 Β· 3 obs
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
●A13.248.169.482026-08-22 β†’ 2026-08-23 Β· 3 obs
β—‹ 2026-05-18 05:49:22
● 2026-08-22 07:27:30
● 2026-08-23 09:49:36
β—‹A172.233.219.1232026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹A172.233.219.492026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹A172.233.219.782026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹A172.237.146.252026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹A172.237.146.382026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹A172.237.146.82026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2019-01-05 23:26:18
● 2026-05-04 19:37:58
β—‹ 2026-05-18 05:49:22
β—‹ 2026-08-23 09:49:36
β—‹A184.168.221.412019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A184.168.221.452019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A184.168.221.522019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A184.168.221.602019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A184.168.221.612019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A184.168.221.622019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A50.63.202.482019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
β—‹A50.63.202.522019-01-05 β†’ 2019-01-05 Β· 3 obs
● 2019-01-05 23:26:18
β—‹ 2026-05-04 19:37:58
β—‹ 2026-08-23 09:49:36
●A76.223.54.1462026-08-22 β†’ 2026-08-23 Β· 3 obs
β—‹ 2026-05-18 05:49:22
● 2026-08-22 07:27:30
● 2026-08-23 09:49:36

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comf.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, h.gtld-servers.net...-
pythonrush.comns1.afternic.com, ns2.afternic.com4 records

βœ… Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pythonrush.com (unsigned zone)

⏱️ Timing

Total: 224ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A276.223.54.146, 13.248.169.48
NS2ns1.afternic.com, ns2.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1.afternic.com dns.jomax.net

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

pythonrush.com has two IP addresses: 13.248.169.48 and 76.223.54.146

dns2.sabaoempo.com, medisales.xyz, hutmo.com and two other host names share IP numbers with pythonrush.com.

Name Servers

The NS records for pythonrush.com delegate to ns1.afternic.com and ns2.afternic.com.

pythonrush.com uses the same name servers as several other domains β€” among them host-219-68-228-99.dynamic.kbtelecom.net, introductionvideos.com, eigenmittel.com and two more.

There is at least partial name server overlap between pythonrush.com and other domains β€” wethrive.co, frontieropenmodels.org, serpanil.com and two more among them.

These name servers frequently co-occur with the name servers verification-a6wcjiy3t6u64zppv78yuf.ns101.verify.hn and verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn.

ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. Likewise, ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45 β€” two IP addresses apiece.