monitorcs.com - dns.ninja
monitorcs.com
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=1784150202 | ||||||
Same first word
monitorcs.com |
monitorcs.ru |
Similar names
DNS History
10 records (9 active, 1 former)
●NSns1.livedns.co.uk2015-08-02 → 2026-07-15 · 2 obs
● 2026-07-15 21:39:24
●NSns2.livedns.co.uk2015-08-02 → 2026-07-15 · 2 obs
● 2026-07-15 21:39:24
●NSns3.livedns.co.uk2015-08-02 → 2026-07-15 · 2 obs
● 2026-07-15 21:39:24
●MXalt1.aspmx.l.google.com2026-03-24 → 2026-07-15 · 5 obs
● 2026-03-24 21:32:04
○ 2026-06-28 21:50:12
● 2026-07-10 04:52:16
● 2026-07-15 21:39:24
●MXalt2.aspmx.l.google.com2026-03-24 → 2026-07-15 · 5 obs
● 2026-03-24 21:32:04
○ 2026-06-28 21:50:12
● 2026-07-10 04:52:16
● 2026-07-15 21:39:24
●MXalt3.aspmx.l.google.com2026-03-24 → 2026-07-15 · 5 obs
● 2026-03-24 21:32:04
○ 2026-06-28 21:50:12
● 2026-07-10 04:52:16
● 2026-07-15 21:39:24
●MXalt4.aspmx.l.google.com2026-03-24 → 2026-07-15 · 5 obs
● 2026-03-24 21:32:04
○ 2026-06-28 21:50:12
● 2026-07-10 04:52:16
● 2026-07-15 21:39:24
●MXaspmx.l.google.com2026-03-24 → 2026-07-15 · 5 obs
● 2026-03-24 21:32:04
○ 2026-06-28 21:50:12
● 2026-07-10 04:52:16
● 2026-07-15 21:39:24
○MXmailserver.monitorcs.com2015-08-02 → 2017-04-08 · 4 obs
● 2017-04-08 16:37:52
○ 2026-03-24 21:32:04
○ 2026-07-15 21:39:24
●A213.171.195.1052015-08-02 → 2026-07-15 · 5 obs
● 2017-04-08 16:37:52
○ 2026-06-28 21:50:12
● 2026-07-10 04:52:16
● 2026-07-15 21:39:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, e.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net... | - |
| monitorcs.com | ns1.livedns.co.uk, ns2.livedns.co.uk, ns3.livedns.co.uk | - |
✅ Authoritative Response
Server:217.160.82.244
NS records: ns1.livedns.co.uk, ns2.livedns.co.uk, ns3.livedns.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for monitorcs.com (unsigned zone)
⏱️ Timing
Total: 474ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 213.171.195.105 |
| NS | 3 | ns2.livedns.co.uk, ns3.livedns.co.uk... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| TXT | 2 | v=spf1 mx a include:_spf.livemail.co.uk , google-site-verification=UyI-XnTWC_yle24 |
| SOA | 1 | ns1.livedns.co.uk admin.monitorcs.com |
Analysis
IP Addresses
monitorcs.com has exactly one IP address — 213.171.195.105.
www.kplzthx.com, reaynlp.com, model-rail-shop-online.com plus two other host names have IP numbers in common with monitorcs.com.
Name Servers
The authoritative name servers for monitorcs.com are ns1.livedns.co.uk, ns2.livedns.co.uk and ns3.livedns.co.uk — three in total.
monitorcs.com partially shares its NS delegation with several other domains, including mitko.net, camhosts.net, stephaniemeyer.co.uk and two others.
These name servers are regularly seen alongside ns1.fast-hosts.org and ns2.fast-hosts.org as name servers.
ns1.livedns.co.uk, ns2.livedns.co.uk and ns3.livedns.co.uk all resolve to exactly two IP numbers apiece: ns1.livedns.co.uk → 217.160.81.244 and 2001:8d8:fe:53:fa::1; ns2.livedns.co.uk → 217.160.82.244 and 2001:8d8:fe:53:fa::2; ns3.livedns.co.uk → 185.132.35.244 and 2607:f1c0:fe:53:185:132:35:244.
Mail Servers
Mail for monitorcs.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by monitorcs.com are shared with other domains: ns500768.ns500759.ns500758.ns500736.ns500698.ns500735.ns500736.ns500698.ns500576.ns500708.ns500576.ns500686.ns500576.ns500619.trackreceptor.com, ns500758.ns500698.ns500758.ns500759.ns500698.ns500698.ns500736.ns500698.ns500698.ns500698.ns500708.ns500698.ns500619.ns500686.ns500619.ns500619.trackreceptor.com, ns500759.ns500759.ns500758.ns500735.ns500736.ns500735.ns500652.ns500619.ns500652.ns500619.ns500652.tracksymphony.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 142.251.167.27 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.