complement.com.sg - dns.ninja
complement.com.sg
com.sg
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ds.sgnic.sg ⭐ | ||||||
| NS | dsany2.sgnic.sg ⚠️ Not in parent delegation | ||||||
| NS | dsany3.sgnic.sg ⚠️ Not in parent delegation | ||||||
| NS | dsany4.sgnic.sg ⚠️ Not in parent delegation | ||||||
| NS | pch.sgzones.sg ⚠️ Not in parent delegation | ||||||
| SOA | ds.sgnic.sgdna@sgnic.sg serial=2608230530 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
15 records (12 active, 3 former)
○NSdnspri.singnet.com.sg2015-06-10 → 2017-06-27 · 4 obs
● 2017-06-27 12:11:04
○ 2026-08-19 08:41:58
○ 2026-08-23 05:55:14
●NSdnssec1.singnet.com.sg2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●NSdnssec2.singnet.com.sg2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●NSdnssec3.singnet.com.sg2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXalt1.aspmx.l.google.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXalt2.aspmx.l.google.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXaspmx.l.google.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXaspmx2.googlemail.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXaspmx3.googlemail.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXaspmx4.googlemail.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●MXaspmx5.googlemail.com2015-06-10 → 2026-08-23 · 2 obs
● 2026-08-23 05:55:14
●A132.226.6.1242026-08-19 → 2026-08-23 · 3 obs
● 2026-08-19 08:41:58
● 2026-08-23 05:55:14
●A140.83.33.652026-08-19 → 2026-08-23 · 3 obs
● 2026-08-19 08:41:58
● 2026-08-23 05:55:14
○A198.185.159.1442016-11-20 → 2017-06-27 · 5 obs
● 2016-11-20 13:17:26
● 2017-06-27 12:11:04
○ 2026-08-19 08:41:58
○ 2026-08-23 05:55:14
○A54.179.184.1982015-06-10 → 2016-04-19 · 4 obs
● 2016-04-19 06:01:50
○ 2016-11-20 13:17:26
○ 2026-08-23 05:55:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| sg | dsany4.sgnic.sg, dsany3.sgnic.sg, pch.sgzones.sg, dsany2.sgnic.sg | - |
| complement.com.sg | dnssec2.singnet.com.sg, dnssec1.singnet.com.sg, dnssec3.singnet.com.sg | 3 records |
✅ Authoritative Response
Server:165.21.100.11
NS records: dnssec2.singnet.com.sg, dnssec1.singnet.com.sg, dnssec3.singnet.com.sg
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for complement.com.sg (unsigned zone)
⏱️ Timing
Total: 1214ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 132.226.6.124, 140.83.33.65 |
| NS | 3 | dnssec3.singnet.com.sg, dnssec1.singnet.com.sg... |
| MX | 7 | ALT1.ASPMX.L.GOOGLE.COM (pri: 20), ASPMX5.GOOGLEMAIL.COM (pri: 30)... |
| SOA | 1 | dnssec1.singnet.com.sg hostmaster.singne |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (dnssec3.singnet.com.sg, dnssec2.singnet.com.sg, dnssec1.singnet.com.sg)
Analysis
IP Addresses
complement.com.sg directs to two IP numbers, 132.226.6.124 and 140.83.33.65
Name Servers
The authoritative name servers for complement.com.sg are dnssec1.singnet.com.sg, dnssec2.singnet.com.sg and dnssec3.singnet.com.sg — three in total.
complement.com.sg has at least partial name server overlap with other domains, such as store-deliver.com, 5.127.203.in-addr.arpa, cscchalets.sg and two others.
Hostnames that resolve to two IP addresses:
dnssec1.singnet.com.sg directs traffic to 165.21.83.11 and 2001:c20:18:a::36.
dnssec3.singnet.com.sg directs traffic to 165.21.100.11 and 2001:c20:10:a::37.
Hosts with just one IP address:
dnssec2.singnet.com.sg has the IP address 165.21.100.11.
Both dnssec3.singnet.com.sg and dnssec2.singnet.com.sg resolve to 165.21.100.11 IP addresses each.
Mail Servers
Mail for complement.com.sg is routed through 7 mail servers, including aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
complement.com.sg has at least partial mail server overlap with other domains such as dmbrisk.com, signcr.com, mimoymima.com and two more.
These mail servers commonly co-occur with mail servers aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx4.googlemail.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
aspmx5.googlemail.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c29::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.