syncrosecurity.com - dns.ninja
syncrosecurity.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=1785475442 | ||||||
Same first word
syncrosecurity.com |
DNS History
18 records (10 active, 8 former)
●NSns1.mysecurecloudhost.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:56:02
● 2026-07-31 05:36:30
●NSns2.mysecurecloudhost.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:56:02
● 2026-07-31 05:36:30
●NSns3.mysecurecloudhost.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:56:02
● 2026-07-31 05:36:30
○NSns3.zadns.co.za2015-07-09 → 2017-03-23 · 4 obs
● 2017-03-23 06:21:58
○ 2020-02-01 05:01:00
○ 2026-07-31 05:36:30
●NSns4.mysecurecloudhost.com2026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:56:02
● 2026-07-31 05:36:30
○NSns4.zadns.co.za2015-07-09 → 2017-03-23 · 4 obs
● 2017-03-23 06:21:58
○ 2020-02-01 05:01:00
○ 2026-07-31 05:36:30
○NSns7.zadns.co.za2020-02-01 → 2020-02-01 · 4 obs
● 2020-02-01 05:01:00
○ 2026-03-24 21:56:02
○ 2026-07-31 05:36:30
○NSns8.zadns.co.za2020-02-01 → 2020-02-01 · 4 obs
● 2020-02-01 05:01:00
○ 2026-03-24 21:56:02
○ 2026-07-31 05:36:30
●MXalt1.aspmx.l.google.com2015-07-09 → 2026-07-31 · 2 obs
● 2026-07-31 05:36:30
●MXalt2.aspmx.l.google.com2015-07-09 → 2026-07-31 · 2 obs
● 2026-07-31 05:36:30
●MXalt3.aspmx.l.google.com2020-02-01 → 2026-07-31 · 3 obs
● 2020-02-01 05:01:00
● 2026-07-31 05:36:30
●MXalt4.aspmx.l.google.com2020-02-01 → 2026-07-31 · 3 obs
● 2020-02-01 05:01:00
● 2026-07-31 05:36:30
●MXaspmx.l.google.com2015-07-09 → 2026-07-31 · 2 obs
● 2026-07-31 05:36:30
○MXaspmx2.l.google.com2015-07-09 → 2017-03-23 · 4 obs
● 2017-03-23 06:21:58
○ 2020-02-01 05:01:00
○ 2026-07-31 05:36:30
○MXaspmx3.l.google.com2015-07-09 → 2017-03-23 · 4 obs
● 2017-03-23 06:21:58
○ 2020-02-01 05:01:00
○ 2026-07-31 05:36:30
●A192.250.229.732026-03-24 → 2026-07-31 · 3 obs
● 2026-03-24 21:56:02
● 2026-07-31 05:36:30
○A197.81.192.482020-02-01 → 2020-02-01 · 4 obs
● 2020-02-01 05:01:00
○ 2026-03-24 21:56:02
○ 2026-07-31 05:36:30
○A197.81.192.502015-07-09 → 2017-03-23 · 4 obs
● 2017-03-23 06:21:58
○ 2020-02-01 05:01:00
○ 2026-07-31 05:36:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| syncrosecurity.com | ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com | 4 records |
✅ Authoritative Response
Server:76.223.26.245
NS records: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for syncrosecurity.com (unsigned zone)
⏱️ Timing
Total: 122ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.250.229.73 |
| NS | 4 | ns4.mysecurecloudhost.com, ns1.mysecurecloudhost.com... |
| MX | 5 | ALT1.ASPMX.L.GOOGLE.com (pri: 5), ALT3.ASPMX.L.GOOGLE.com (pri: 10)... |
| TXT | 1 | v=spf1 +a +mx +ip4:192.250.229.11 includ |
| SOA | 1 | ns1.mysecurecloudhost.com robert.phnx.ag |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com...)
Analysis
IP Addresses
syncrosecurity.com resolves to just one IP address, 192.250.229.73.
Two other host names, along with bol-brac.com, 3rft.com and get-host.net, also share IP numbers with syncrosecurity.com.
Name Servers
The NS records for syncrosecurity.com point to four name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com.
There is at least partial name server overlap between syncrosecurity.com and other domains — telewiring.com.my, glimedia.com, dkkitchenappliances.com and two more among them.
These name servers regularly appear alongside ns1.supercp.com, ns2.supercp.com, ns3.supercp.com and 3 other name servers in NS record sets.
The hosts ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com all resolve to exactly one IP address each: 13.248.158.180, 75.2.118.134, 76.223.26.245 and 99.83.147.209 respectively.
Mail Servers
syncrosecurity.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between syncrosecurity.com and other domains, including ns500765.ns500693.ns500693.ns500699.ns500693.ns500699.ns500699.ns500588.ns500693.ns500699.ns500699.ns500693.ns500699.ns500612.ns500632.ns500110.dtrkdll.com, ns500698.ns500698.ns500698.ns500758.ns500698.ns500736.ns500698.ns500736.ns500735.ns500708.ns500619.ns500698.ns500576.ns500619.ns500576.trackreceptor.com, ns500698.ns500698.ns500758.ns500758.ns500759.ns500735.ns500735.ns500735.ns500708.ns500652.ns500652.ns500576.ns500619.tracksymphony.com and two others.
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.
Host names that have two IP addresses:
aspmx.l.google.com resolves to 142.251.167.27 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 74.125.193.27 and 2a00:1450:400b:c01::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.