sirserv.com - robtex.com
sirserv.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 107.163.47.15🇺🇸 AS395776107.163.47.0/24 SKBroadband customer route | ||||||
| NS | ns1.dns.com ⭐ | ||||||
| A | 2001:df2:f080:2::1:1🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.23.191.128🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.86.21.128🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| NS | ns2.dns.com | ||||||
| A | 2001:df2:f080:2::1:2🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.23.191.129🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.86.21.129🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| SOA | ns1.dns.comadmin@dns.com serial=1765844194 | ||||||
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=1782297820 | ||||||
rank #420386 in the tld
Previously MX for
sirserv.com |
Same first word
sirserv.com |
Similar names
DNS History
17 records (3 active, 14 former)
●NSns1.dns.com2026-06-13 → 2026-06-24 · 3 obs
○ 2018-10-02 03:18:04
● 2026-06-13 09:52:18
● 2026-06-24 11:12:14
● 2026-06-13 09:52:18
● 2026-06-24 11:12:14
○NSns1.mxserver.ro2015-07-07 → 2015-07-07 · 3 obs
● 2015-07-07 07:21:16
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
●NSns2.dns.com2026-06-13 → 2026-06-24 · 3 obs
○ 2018-10-02 03:18:04
● 2026-06-13 09:52:18
● 2026-06-24 11:12:14
● 2026-06-13 09:52:18
● 2026-06-24 11:12:14
○NSns2.mxserver.ro2015-07-07 → 2015-07-07 · 3 obs
● 2015-07-07 07:21:16
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○NSns47.domaincontrol.com2017-01-29 → 2017-01-29 · 4 obs
○ 2016-06-17 21:17:00
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
○NSns48.domaincontrol.com2017-01-29 → 2017-01-29 · 4 obs
○ 2016-06-17 21:17:00
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
○NSns7.rookdns.com2016-02-24 → 2016-06-17 · 5 obs
○ 2015-11-18 09:28:56
● 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
● 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
○NSns8.rookdns.com2016-02-24 → 2016-06-17 · 5 obs
○ 2015-11-18 09:28:56
● 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
● 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
○MXmail.mxproc.com2016-02-24 → 2016-02-24 · 4 obs
○ 2015-11-18 09:28:56
● 2016-02-24 14:37:48
○ 2016-06-17 21:17:00
○ 2026-06-24 11:12:14
● 2016-02-24 14:37:48
○ 2016-06-17 21:17:00
○ 2026-06-24 11:12:14
○MXmail.replyingback.com2016-06-17 → 2016-06-17 · 4 obs
○ 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
○MXmailstore1.secureserver.net2017-01-29 → 2017-01-29 · 4 obs
○ 2016-06-17 21:17:00
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
○MXsirserv.com2015-07-07 → 2015-07-07 · 3 obs
● 2015-07-07 07:21:16
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○MXsmtp.secureserver.net2017-01-29 → 2017-01-29 · 4 obs
○ 2016-06-17 21:17:00
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
●A107.163.47.152026-06-13 → 2026-06-24 · 3 obs
○ 2018-10-02 03:18:04
● 2026-06-13 09:52:18
● 2026-06-24 11:12:14
● 2026-06-13 09:52:18
● 2026-06-24 11:12:14
○A141.8.224.932016-02-24 → 2016-06-17 · 5 obs
○ 2015-11-18 09:28:56
● 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
● 2016-02-24 14:37:48
● 2016-06-17 21:17:00
○ 2017-01-29 17:20:26
○ 2026-06-24 11:12:14
○A188.213.20.1822015-07-07 → 2015-07-07 · 3 obs
● 2015-07-07 07:21:16
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○ 2015-11-18 09:28:56
○ 2026-06-24 11:12:14
○A50.63.202.382017-01-29 → 2017-01-29 · 4 obs
○ 2016-06-17 21:17:00
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
● 2017-01-29 17:20:26
○ 2018-10-02 03:18:04
○ 2026-06-24 11:12:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| sirserv.com | ns1.dns.com, ns2.dns.com | 6 records |
✅ Authoritative Response
Server:154.23.191.128
NS records: ns1.dns.com, ns2.dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sirserv.com (unsigned zone)
⏱️ Timing
Total: 306ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 107.163.47.15 |
| NS | 2 | ns1.dns.com, ns2.dns.com |
| SOA | 1 | ns1.dns.com admin.dns.com |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.dns.com, ns1.dns.com, ns1.dns.com...)
Analysis
IP Addresses
sirserv.com resolves to one IP address: 107.163.47.15.
zzdcu.com, hnyzw6.com, large-farming-square.com and two other host names share IP numbers with sirserv.com.
Name Servers
sirserv.com uses two name servers for its delegation: ns1.dns.com and ns2.dns.com.
sirserv.com uses the same name servers as several other domains — among them naxin-cl.com, 697ty.com, 888888p.com and two more.
ns1.dns.com and ns2.dns.com each resolve to three IP addresses. ns1.dns.com resolves to 154.23.191.128, 154.86.21.128 and 2001:df2:f080:2::1:1. ns2.dns.com resolves to 154.23.191.129, 154.86.21.129 and 2001:df2:f080:2::1:2.