parascheduler.com - robtex.com
parascheduler.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 216.68.135.116🇺🇸 FUSE-NET216.68.128.0/17 | ||||||
| PTR | 116.135.68.216.ded-dsl.fuse.net | ||||||
| NS | dnsr02.dns2go.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 192.168.200.15 | ||||||
| NS | ns1.dns2go.com | ||||||
| A | 67.217.38.34🇺🇸 AS2245867.217.38.0/24 | ||||||
| PTR | ns1.dns2go.com | ||||||
| NS | ns2.dns2go.com | ||||||
| A | 67.217.34.232🇺🇸 AS2245867.217.34.0/24 | ||||||
| PTR | ns2.dns2go.com | ||||||
| NS | ns3.dns2go.com ⚠️ Not in zone NS records | ||||||
| A | 127.0.0.1 | ||||||
| NS | ns5.dns2go.com ⚠️ Not in parent delegation | ||||||
| A | 67.217.38.38🇺🇸 AS2245867.217.38.0/24 | ||||||
| PTR | ns5.dns2go.com | ||||||
| MX | parascheduler.com ⭐ | ||||||
| A | 216.68.135.116🇺🇸 FUSE-NET216.68.128.0/17 | ||||||
| PTR | 116.135.68.216.ded-dsl.fuse.net | ||||||
| SOA | dnsr02.dns2go.comadmin@dns2go.com serial=20090291 | ||||||
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=1771291435 | ||||||
MX for
parascheduler.com |
Same first word
parascheduler.com |
DNS History
12 records (7 active, 5 former)
●NSdnsr02.dns2go.com2026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
●NSns1.dns2go.com2026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
●NSns2.dns2go.com2026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
●NSns3.dns2go.com2026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
○NSns37.domaincontrol.com2015-05-30 → 2018-11-14 · 4 obs
● 2018-11-14 12:32:18
○ 2026-02-23 10:45:40
○ 2026-03-23 18:52:00
○NSns38.domaincontrol.com2015-05-30 → 2018-11-14 · 4 obs
● 2018-11-14 12:32:18
○ 2026-02-23 10:45:40
○ 2026-03-23 18:52:00
●NSns5.dns2go.com2026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
○MXmailstore1.secureserver.net2015-05-30 → 2018-11-14 · 4 obs
● 2018-11-14 12:32:18
○ 2026-02-23 10:45:40
○ 2026-03-23 18:52:00
●MXparascheduler.com2026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
○MXsmtp.secureserver.net2015-05-30 → 2018-11-14 · 4 obs
● 2018-11-14 12:32:18
○ 2026-02-23 10:45:40
○ 2026-03-23 18:52:00
●A216.68.135.1162026-02-23 → 2026-03-23 · 3 obs
● 2026-02-23 10:45:40
● 2026-03-23 18:52:00
○A50.63.202.482015-05-30 → 2018-11-14 · 4 obs
● 2018-11-14 12:32:18
○ 2026-02-23 10:45:40
○ 2026-03-23 18:52:00
🔍 DNS Trace
Analysis
Mail Server Role
The mail server for parascheduler.com is parascheduler.com.
IP Addresses
parascheduler.com maps to IP address 216.68.135.116.
Other host names, for example, 116.135.68.216.ded-dsl.fuse.net share IP numbers with parascheduler.com.
Name Servers
parascheduler.com delegates to five name servers: dnsr02.dns2go.com, ns1.dns2go.com, ns2.dns2go.com, ns3.dns2go.com and ns5.dns2go.com.
parascheduler.com at least partially shares name servers with other domains such as 101main.net, pittsburghbluesharp.com, linux-site.net, dynamic-site.net and sojogos.com.br.
these name servers are commonly used with the name servers dnsr02.deerfield.com.
Host names with one IP number:
dnsr02.dns2go.com points to 192.168.200.15
ns1.dns2go.com points to 67.217.38.34
ns2.dns2go.com points to 67.217.34.232
ns3.dns2go.com points to 127.0.0.1
ns5.dns2go.com points to 67.217.38.38
Mail Servers
One mail server serves parascheduler.com.
parascheduler.com points to one IP number: 216.68.135.116.